As the author of this plugin I'm obviously biased.
I realise that giving the user the capability of defining their own CSS could be just as dangerous as giving them access to TinyMCE. But if it saves the author time then it can also save them money.
I used to frown upon the use of internal CSS, but now I'm a big fan. Using internal CSS can help reduce the size of the CSS file delivered to the browser. It's also less likely to adversely affect the formatting of other pages.
Note: internal CSS, also known as embedded CSS, is the stuff that is put in the style tags. This is different from inline CSS - which is defined with the style tag.
I did have one niggle, which was that I had to fiddle with filters to handle strange behaviour with wpautop() processing. But I'm not the first person to have suffered this and won't be the last.
The problem was that there was a chance that activating this plugin would break the formatting of content that relied on certain side effects of the default filters run for 'the_content'.
In v0.8.0 the autop processing has been improved. The
The oik-css plugin is great for creating custom CSS just where it's needed. It's especially useful when you want to apply some styling to a specific field on a specific page. I often combine it with oik shortcodes to override default behaviour.
Note: I also use the oik custom CSS AND/OR Jetpack's Edit CSS option.
You must log in to submit a review. You can also log in or register using the form near the top of this page.