Hey @bottlecapnapkin,
Thanks for posting!
Our builder only takes over a post or page once it is launched manually, it doesn’t do it automatically.
The builder must have been launched on that page/post at some point and its layout published as that is the only time the builder overwrites the content within the native WP editor. You can check the article we have below for more info. 🙂
https://kb.wpbeaverbuilder.com/article/129-data-storage
Not sure what you mean by the layout is broken though. Are you referring to the native WP editor content’s layout? Or our builder’s?
Ben
The broken layout is due to inline styles being removed from the WP editor content. I’m not sure how if would have been possible for someone else to go in and activate beaver builder on this page without that content being stripped out.
As described in my initial post, when looking at the list of pages, the page in question was clearly tagged “Classic Editor,” but when opening it up to edit, I got the dialog that it was a beaver builder page. That in itself is not normal or expected behavior.
The only solution that worked for me was to deactivate/remove beaver builder from the site.
Hey @bottlecapnapkin,
Apologies for the delayed response here.
It definitely isn’t as the builder doesn’t launch itself automatically on posts. And it doesn’t override the classic WP editor data until its layout is published.
If you’re interested, and if it’s enabled on your site, you can check the page’s Revisions. An entry is logged there each time a layout is published. 🙂
Ben
Yeah, I’m not sure why this happened. As I mentioned initially, before opening the page, beside the page title was the text “Classic Editor.” When opening the page to edit, it said something to the effect that this was a Beaver Builder page. The only way to recover the original code was to restore from backup. So any revisions that could indicate what happened were lost at that point.
Hopefully this was due to a plugin conflict or other anomaly and it doesn’t happen to other users. Luckily there was no content that actually used Beaver Builder on the site so deleting the plugin solved the issue.
Hey @bottlecapnapkin,
It was most likely isolated to your site or a one-time thing as we would have a lot more tickets if it was a widespread issue.
Anyhow, glad to hear you fixed it. And thanks for taking the time to inform us! 🙂
Ben
