Updated from v3.3 – code not displaying correctly

Hi @t1dhvls,

I’m looking into this right now. Thanks for the bug report! I’ll post back soon.

John

@t1dhvls,
Could you let me know which version of WordPress you are using and where you are seeing the code display in a single column? Is it in the editor on the Settings page, or in the customizer?

Thanks!

John

@t1dhvls,

Also a screenshot and/or a sample of your code would help me diagnose this more quickly.

Thanks again,

John

Running WP 4.8.5, but updating to 4.9.x shortly.

Appearance | Custom CSS — while loading the Custom CSS page it displays correctly, but then displays goes to the view as shown in link below.

Here’s a screenshot link: https://www.screencast.com/t/INsjkYSGbU

I hope this helps. Thanks for the quick response!

@t1dhvls

Thanks for taking the time to send me back this information. It’s really helpful. I’m wondering if this is a plugin conflict. If not, it may be an issue with using an older version of WP, which is definitely a concern for me as a developer, because I want to be sure the plugin is backward-compatible.

This appears to be a JS conflict somewhere, but I can’t be sure about that. It could even be something with the CSS.

Could I ask you to deactivate your other plugins and see if the issue goes away? And if it does go away, could you isolate which plugin is causing the conflict, or maybe let me know what plugins you are using so I can test?

This would be really helpful and help me diagnose an issue others may be having.

Thanks for your help to make this a better plugin!

John

I’m using WordPress 4.5.13 and my custom css is in vertical format and not editable neither after upgrade to 4.0 of Simple Custom CSS.

Where is the custom css codes stored in server? I want to be able to create a backup of it since I cannot copy and paste the information that I already have in my stylesheet.

I only see PHP files and a readme text in the wp-content/plugins/Simple Custom CSS folder.

An update for this issue has been pushed. Please update your plugin and let me know if this is resolved, @t1dhvls

Thanks for the feedback!