Something with beaver builder is messed up…
When you guys resave the _fl_builder_data and _fl_builder_data_settings the data is serialized differently breaking the page layout…
Also _fl_builder_enabled is not being set…
Compare Working Version
http://www.flowpress.com/screenshots/screenshot%202019-04-11%20at%209.23.46%20AM.png
To Your Version After Saving BB layout with restricted user (which should force a revision)
http://www.flowpress.com/screenshots/screenshot%202019-04-11%20at%209.25.21%20AM.png
So when the page goes through a revision the layout just breaks and isn’t rendered.
In the current beta version, pending revisions of Beaver Builder posts work as with other editors, but we have not yet developed the custom UI manipulation to indicate that a pending revision will be (or was) created instead of a direct edit. If unsure of which was done, reload the post’s public URL after the edit.
Note that you can only use Beaver Builder to submit revisions to posts that were previously created or edited with Beaver Builder.
Keep in mind this is an unreleased beta. I’ll let you know if I need help recreating the error you mentioned.
The problem is on line 479 it’s an array within array… one too many arrays being set
http://www.flowpress.com/screenshots/screenshot%202019-04-11%20at%209.35.57%20AM.png
Thanks Kevin,
Do you think we can add some JS to replace the publish button so it’s super clear that the user is creating a revision? Otherwise it’s very confusing to end users.
@raptor235, I’ve updated the Revisionary development version to correct the post_meta array issue.
Be aware that Revisionary does not currently support revisioning of post meta in general, and this code should not be taken to imply that it does or should. Custom field revisioning functionality will be developed for Revisionary Pro.
This pertains only to Pending Revision creation and approval support we are volunteering for whatever Beaver Builder stores to the _fl_builder_data and _fl_builder_settings meta fields.
If customization of the Beaver Builder front end editor UI would be a significant value to you or your clients, consider sponsoring expedited development of that particular feature. Failing that, maybe you can find the budget to either educate your users about the revision process or come on board with Pro once those features are available.
