Hello,
I downloaded the latest version of CSS Editor today and noticed that the inspector feature is gone. Was it removed? Or do I possibly have a conflict with another plugin? If it was removed, is it possible to downgrade to the previous version?
Thanks :)
Hi Tam
It should still be there. Can you check if clearing your browser cache fixes the issue? This was a fairly significant update.
https://codex.wordpress.org/I_Make_Changes_and_Nothing_Happens#Clearing_the_Browser_Cache
Can you also check if you’re getting any Javascript errors? This will help us figure out what’s causing the issue in your case if it’s not cache related.
https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors#Step_3:_Diagnosis
I have the same problem. I try clean the brownser cache, without results. I checked the errors in my browser, please see the image… http://prntscr.com/cn00ar
Hi Lincoln
Thanks for the link. Strangely, that error is from a 3rd party CSS parsing library. I see you’re using Firefox, can you check which version so I can test?
Hi Greg,
Clearing the cache didn’t work for me.
Here are the errors in my browser: http://prnt.sc/cn3xk0 & http://prnt.sc/cn3y4d
I am using Chrome Version 53.0.2785.116 m.
Thank you
I haven’t been able to recreate this issue on my side, but it might have something to do with the CSS initially entered in the editor. Can anyone who’s getting this issue post their custom CSS here for me to check with?
Hi Everybody,
Just tried on Windows 10 and wasn’t able to replicate any of the issues described. The latest update is actually quite a large one so it’s quite possible new conflicts may have been introduced. As such, please be sure to try a plugin conflict test to rule this out.
For reference, here’s the typical plugin conflict test:
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.
Hi Alex, i tried in a new wordpress instalation, it’s working fine :(
I will try disabling all non-siteorigin plugins…
Greg & Alex,
Disabling all my plugins made no difference. It works fine when I switched to one of the default themes.
You can see my code here: http://textuploader.com/da5ug
Tam R Paul, the same happens to me
Which theme are you all using?
I am using Sugar Blog : https://themeforest.net/item/sugarblog-clean-personal-wordpress-blog-theme/12900311
So from the looks of things, the minification library we were using (npm-uglify) was breaking the CSS parser library. I’m going to try fix up the build script and release an update.
I’ll post the update here for testing first. I’m unable to recreate the issue on my side, but I’ve logged into an install where the issue is happening, so I can see what’s going on.
Hi everyone
So it turns out this issue was coming up because of malformed CSS in the front end of a site (coming from either a theme or a plugin). I changed a few things to make SiteOrigin CSS handle these errors a lot better. Everything seems to be working properly now. If you’d like to test this, please try out version 1.1.1.
so-css-1-1-1
I’ll prepare a release with in the next few hours.
Greg, I tried the new version, and it works for me, I am using the theme “Rookie” … thank you very much for your help, I really appreciated.
It's a pleasure :) – very glad we could get this issue fixed.
Hey Greg,
Just wanted to say I was having similar issues and the update has fixed them. Don’t think enough people say thank you these days so wanted to throw one out there. Thanks for the great plugin too!
It’s an absolute pleasure, Shaun! Thanks for the awesome feedback.
It worked for me as well! Thank you and your team so much for your help :)