Forum Replies Created
-
AuthorPosts
-
meta_gecko
ParticipantHey, thanks for that, although I think you're missing the point.
We should not have to rely on a reply to a forum post if we need to roll back a version of a premium plugin.
As you stated above, the link will be removed after a few days. The point is that as paying customers we should have permanent access to previous versions from within our account area for as long as we have an account with you.
Please reconsider your current standpoint. As customers we also want to have the latest version installed, but only if it works. If there is a problem we should have the option to roll back until the problem is resolved without needing to wait at all.
Thanks
ParticipantHi, this is a really strange thing to force on customers and could potentially cost them money as well as valuable time.
While it is the responsibility of the site owner to take backups before updating plugins, there are many, many, many people who do not do this.
Denying us access to previous versions means that if an update breaks the site, and a backup was not made, we have no recourse other than to wait for support to help.
This could take hours, or a day, or sometimes it might take 3 days.
Please allow your customers to download previous versions of an addon (AIO especially). We can roll back the core MB plugin no problem because it's in the repo, so why are we denied access to previous versions of the tools we have paid for?
ParticipantHi Anh,
It works fine, but when you add a custom capability then that capability needs to be given to any roles who need it, including administrators.
This isn't the responsibility of Meta Box, it's up to the admin to provide the appropriate permissions to any roles that need it.
The only thing I'd suggest is that you might want to add some information to the documentation because many people won't know this otherwise.
ParticipantJust to confirm, adding
'map_meta_cap' => true,solves the problem. Doing so maps all of the primitive capabilities to the custom capability.ParticipantHi Anh,
Thanks for this, however it doesn't appear to be complete. The custom capability is added, however the capabilities do not appear to be mapped to the core caps required by administrators (or any one else who is granted the capability) to edit published posts etc.
There should be at least 11 capabilities for the admin role.
*edit. adding all of the capabilities might not be necessary since they should be inherited.
It seems that when registering the CPT using MB the mapping of the capabilities are missing:
'map_meta_cap' => true,ParticipantAny updates on this request? Unfortunately need to create own types for now because of the capabilities limitation..
July 21, 2018 at 6:50 AM in reply to: Latest Update 4.15.0 has some problems - Buttons field, maybe more #10651ParticipantJuly 16, 2018 at 7:44 PM in reply to: oEmbed Field Connection prints message on front end when empty #10590ParticipantThanks, I've cloned the repo, will test it later this afternoon.
July 15, 2018 at 8:01 PM in reply to: oEmbed Field Connection prints message on front end when empty #10579ParticipantThanks Anh, appreciate it.
July 14, 2018 at 10:17 PM in reply to: oEmbed Field Connection prints message on front end when empty #10567ParticipantI'm stumped on this one. I removed that annoyance manually for the moment, but obviously it will keep coming back with every update so I need to find how to fix this permanently please.
I don't understand why that check is hardcoded into the field with no options to turn it off from the field parameters?
Also would like to be able to change the wording with a filter in the cases where it might be useful to display a message.
Also, why is it printing out on the front end of the site? If you are going to do that then at least wrap the message with a CSS class of its own so that it can either be removed with CSS, JS, and or/styled to look more attractive.
Thanks, looking forward to a resolution.
ParticipantHi Anh,
It seems this is a limitation with Themer.
Currently, only string values will be returned as objects, and arrays are not currently supported by field connections.
I'm not sure what the solution is, although it would probably save some confusion if this connection was removed and a request sent to Beaver Builder to start adding some notes about the known limitations to their knowledge base (and it would be helpful if you added this to the documentation of the connector plugin too).
Fortunately I don't need any too complex with the current site, so I can fudge my way around it.
I might just decide to dump Themer for the Singular layouts and go back to normal WordPress since the layouts are extremely basic...
ParticipantHi Anh, that did the trick, thanks 🙂
ParticipantHi Alexander,
As far as I know this isn't possible at the moment.
I'm basing my reply on this question that I asked some time ago.
It's not quite the same question, but the reply indicates the current integration is somewhat limited, and the developers are keen to get ideas about how to improve it.
Thinking about it "on the fly" so to speak, to add your own custom field types to the builder addon would mean modifying the code of the addon itself, and I'm not aware of any hooks that allow for this right now.
June 23, 2018 at 7:10 PM in reply to: Please allow developers to remove the Dashboard from the new Global menu #10330ParticipantGreat, thanks Anh.
I was thinking that it is nice to have all the direct links to the documentation and support, so please don't waste too much time on this unless there are more people asking for the same thing.
ParticipantHi Anh,
Thanks, this works perfectly.
-
AuthorPosts