You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Some issues with Page Builder content in the_content()(normal post content) if an ACF Page Builder field is rendered before the_content(). We recommend using ACF Page Builder fields instead and removing the normal post content completely on ACF-pages in WP-Admin."
So in my posts, my main content uses Page Builder, and then I have a custom field (using ACF) that uses your plugin's "Page Builder" field type.
On the first post, it displays correctly, but on the second post and on, the layouts get messed up. It seems to be affecting the ID's of subsequent posts thus not allowing the CSS that gets injected into the footer by Page Builder to match to the post correctly.
Let me know once this is fixed, because it's pretty much unusable until then.
The text was updated successfully, but these errors were encountered:
We have been investigating this before. Unfortunately, it's not an easy fix because of the way the Page Builder plugin works. As there is a good(in our opinion) workaround for this we didn't feel it was worth the effort to fix.
Isn't it possible to just use the workaround with an ACF Page Builder field instead of using the page builder in the main content? We haven't come across any issues with this approach.
If that doesn't work for you, please explain why and we might reconsider this.
This is kind of a deal breaker to me:
So in my posts, my main content uses Page Builder, and then I have a custom field (using ACF) that uses your plugin's "Page Builder" field type.
On the first post, it displays correctly, but on the second post and on, the layouts get messed up. It seems to be affecting the ID's of subsequent posts thus not allowing the CSS that gets injected into the footer by Page Builder to match to the post correctly.
Let me know once this is fixed, because it's pretty much unusable until then.
The text was updated successfully, but these errors were encountered: