John Regan

Hey, Jamer! Thanks for the great review!

marking as resolved.

Hi zzbloggerzz. Thanks for the question! Unfortunately it sounds like Simple Custom CSS is not compatible with that CSS editor. There is no stylesheet to edit in this plugin; it saves the styles you input into the database, then dynamically renders it, using a technique that tells the browser that there’s a CSS file, when there really is none.

If I can answer any other questions for you, just ask!

Hi @intellegentDesign. Thanks for the input! You make some great points here that I will take to heart; they would have great ideas to put into a support ticket. ?? I’m going to consider them for v. 1.3. Thanks again!

@intelligentdesign, I’m glad you got it worked out!

Glad I could help!

Yep. that’s exactly why this plugin exists. It saves your css changes to the database, instead of writing them to a CSS file that can be overwritten or deactivated when WP or a theme is updated. Does that answer your question?

I’m glad to help you, maomaohu. I’m not exactly sure what you mean when you say “custom CSS gets overwritten.” What custom CSS are you speaking of? The CSS you’ve entered into this plugin, or somewhere else?

Thanks for recommending my plugin!

Hi @jaldenleonard. Sorry about the issue with my plugin. I hope the latest version works great for you. Thanks for using Simple Custom CSS!

Marking as resolved.

Hi Siobhan,

It turns out that as I was escaping the content of the CSS the “>” was getting stripped out. As a Front End dev at heart, I understand what a big deal this is.

Long story short, it’s fixed. Please update to version 1.1.1.

Thanks again for your input. I’m sure that there are other people having this issue. Thanks for helping me make this plugin better!

I think I might know the culprit. I’ll take a look at it and get back with you shortly. Thanks for the note!

Ha! Thanks for bringing this up. I hate to admit it, but I didn’t know register_unistall_hook() existed. I thought there was only activation and deactivation hooks. I’m going to add this to the next version!

Thanks @tristandenyer!

I printed the CSS to the header to ensure it superceeded any other styles. Admittedly, I’m not a huge fan of doing that. I like to keep things nice and neat. I thought about creating a psuedo-css file (called something like style.php) which would echo the styles into using PHP, but that would require seeking out wp-load.php in that file, which would add an extra load on the site.

However, I think I’ve found a work-around. I’m looking at dynamically creating a psuedo-stylesheet that will be enqueued like a stylesheet, and show up in the Page source as a link to a css file (e.g., <link rel=”style.css” />), but it will actually be generated within the single PHP file this plugin includes–it still will not create another file. I’ll probably release that within a week or so. I won’t affect any settings that already exist, it will just be a cleaner way to apply the CSS.

I opted to not delete the Options field on deactivation because I know sometimes people deactivate plugins when they’re tracking down bugs, and if you’ve done a lot of work on your CSS, it would be a bummer to lose it all. I figure it’s just one options field, with (typically) a lightweight level of content. I’ve seen plugins use a checkbox that says “delete all data from database when deactivated.” I might try that.

Thanks for the idea about adding the option to add credit to the CSS. I wasn’t sure if that kind of thing would be a bother or not. I want to be careful that I keep the “Simple” in “Simple Custom CSS.” ??

I really appreciate the input. It really helps me out. I want to make Plugins that people love!