Plugin Contributor
alexgso
(@alexgso)
Hi ubernerd,
Can you please clarify what changes you’re trying to make that aren’t applying? I ask as I’ve just tried to make a few changes using the Visual Editor and it worked without issue for me.
After I updated SiteOrigin is not applying any custom CSS settings, not just new ones I am trying to insert. I had even reverted to an older version/revision from last week that worked and it still was not applying custom CSS. Seems like the CSS is being ignored completely. Never experienced a problem before with SiteOrigin on other sites so I am chalking it up to some change in 1.2.2 causing it. No other updates or other changes were made to the site other than the CSS plugin update.
Plugin Contributor
alexgso
(@alexgso)
Hi ubernerd,
That’s odd. Can you please temporarily update SiteOrigin CSS and then run a plugin conflict test? For reference, here’s the typical plugin conflict test we recommend:
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.
My situation looks like above but is much more weird. This issue has been fixed I can confirm that.
Now with version 1.2.3 a completely new bug appeared. Sometimes CSS is implemented, sometimes it isn’t and even worse sometimes it creates its own CSS. It has taken me many hours before I finally understood that it was again this plugin that made my life miserable…
The final fix was using another way of storing the CSS changes, but then there is no use anymore for this plugin. The alternative was switching back to version 1.1.2 which I have setup now.
I have even looked up the database storage and deleted them. Having a complete new install, still somehow the plugin managed to find and reuse previous CSS.
I really like the plugin, but I have had more then my share of troubles with the latest updates!
Hi @evolinestore
Sorry about the recent update issues. If you have a moment to open a new support topic we can help address the two issues highlighted above. Please let us know what CSS the plugin was creating on its own in that new topic. We’ll attend ASAP. Thanks.
