Hi,
I created a page with the pagebuilder. Within the input-field, I added a div-tag with a style-attribute. The CSS within applies fine for logged-in users, but seems to be gone when I log out myself.
When i look at the page’s source, I find my div, but the style-attribute is completly gone.
Could you give me any hints why this happens?
Hi Simon
Do you have a public URL where we can take a look at what’s going on? If you need to keep this URL private from other users, just select “Private Reply” on the bottom right of the comment box.
Please, indicate the area of the page we should be checking, thanks.
This is a private message.
Thanks for the feedback. Could you perhaps, check the initial login details provided, we’re currently unable to login with those. Thanks.
This is a private message.
This is a private message.
This is a private message.
This is a private message.
This is a private message.
Thanks for the update. Try clearing WP Super Cache’s cache.
Doesn’t change anything. Also, disabling the cache completly within the plugin doesn’t help.
Try clearing the cache in WP Super Cache and then deleting the plugin completely. We can come back to caching once we’ve narrowed this down.
No changes without the plugin
Hi Simon
We’re not sure why this is still happening. It’s unusual and almost always caching related. Try doing a complete plugin conflict test. Instructions below:
This sounds like it could be a plugin conflict issue. Can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.
I had the same problem today.
Inside a text editor field I put a style instruction for a background image.
When being logged in everything was fine. Being logged out the background image wouldn’t show.
I disabled all plugins but the Page Builder Plugin and then it worked!
By enabling the plugins one after another I found the reason for the error.
It’s the SiteOrigin Widgets Bundle!
Unfortunately the Page Builder does not work for editing without the Widgets Bundle.
However the created pages are shown properly, even if the Widgets Bundle is disabled.
For reproducing the error and to find a solution here are the versions I am using:
– WordPress 4.4
– SiteOrigin Page Builder 2.2.2
– SiteOrigin Widgets Bundle 1.5.4
The CSS instruction I use in a text editor widget is:
Horst
“”””
“”// “”
“”””
Hope the style assignment shows up now!
Now as a picture.
Hi Horst
We’d like to help you, but can you please start a new thread with your question? We can only offer you the best support possible when you’re the owner of a thread.
Page: New Thread
If you’re a premium user, please be sure to enter your order number so we can properly prioritize your thread.
Deactivating all plugins did help. When reactivating them one by one, it broke again after activating the SiteOrigin Widgets Bundle.
This is reproducible, it works when the Widgets Bundle is active and breaks when I activate it again.
Have you tried testing with only SiteOrigin plugins activated? It’s possible there is a three-way challenge. Try testing with only SiteOrigin plugins activated and see how that goes.
Also happens with only PageBuilder and the Widgets Bundle activated
Thanks for all your testing. Please, enhance our WordPress user account to Administrator so we can take a further look.
Done. Your user has admin-rights, now.
Thanks. I’ve moved the inline styles to a class at Appearance > Custom CSS. It’s resolved the challenge. Hope you’re happy with that workaround.
I’d prefer to understand why this happened and what can be done to deal with it, instead of working around, but it’s fine for the moment, thanks.
I understand. Separating markup and style using a class is ideal and more in line with standards so we’re not downgrading to a lesser solution. Unfortunately, I’m not sure where the issue is at this point. I’ve logged the bug for our developers to check out when they’re able. Thanks for reporting and helping make Page Builder a better plugin.