I assume that what I am asking about is being saved in the post meta. Advanced Custom Fields data is preserved when merging back into the page but if I allow them to have those fields on the alternate post custom post type they don’t see the original data and can overwrite the custom field info without having the original to work from.
Also we were using User Access Manager which seemed to be working great. The group assignment is done in a meta box in the page. When editing the alternate version the group is checked but upon merging back into the original that value is lost and the access is wide open again.
I’ve tried your section groups but it isn’t exactly what we are looking for. UAM hides all pages except the ones that are assigned to the group thus only allowing them to clone those pages.
Any help with this is greatly appreciated.
Looks like there are ways to get Version to jive with mods that require custom fields, but it’s highly specific. If you figure out the ACF issue, kindly link to your solution. Thanks!
Currently plugins that utilize post meta / custom meta boxes need to explicitly add support for the BU Versions plugin in order to work properly. There are a couple open issues in our Github repository with discussion around this decision:
We are kicking around some ideas to smooth out this experience in a future release.
The workflow we envisioned when creating these plugins was to limit full editing capabilities to specific pages with BU Section Editing, but give the ability to suggest changes to all content with BU Versions. With this setup “Section Editors” can create alternate versions for pages they are not allowed to edit and then “Submit for Review”. (By default, section editors are not allowed to edit any published content).
- The topic ‘Post Meta cloning’ is closed to new replies.