More advanced setting for enable/disable many feature:
Enable/Disable invisible elements;
Enable/Disable print margin;
Enable/Disable line numbers;
Enable/Disable backups (end, if enabled, save only if exist data to save = no more empty backup)!
Enable/Disable autocomplete;
All setting saved with cookies only when an admin access in backend!
2.9
Added version querystring in css and javascript (prevent cache issue from old release).
2.8
More code change/fix/clean (expecially in textarea and search bar) + removed old codemirror fix.
2.7
Search bar no longer fixed (caused graphics problems in some circumstances)
2.6
Fix a bug with 2.5 in svn repository!
2.5
More code clean, fix, and optimization!
All string translated (also in backup pages)!
Now with live auto-complete; text-zoom; theme-changer; and search bar!!!
2.4
More code clean, bugfix, optimization and performance!
Now support https and fix incompatibility issue with blue admin plugin!
2.3
Some code change/fix and now use Ace (Ajax.org Cloud9 Editor) instead of CodeMirror !!! 😀
2.2
More code clean/rewrite/optimization!
my_style.css no more deleted if blank (but still no show in output)…
Now script generate blank index.html page for prevent directory listing
File now in “wp-content/uploads/” directory (i hope this can fix some issue with some server – sorry, i prefer to don’t touch/old user file via script – so, move yourself if u glad)!
Top button improved with code of another my plugin: smooth-page-scroll-to-top (some little code only for this page – a good jquery effect)!
Now only one (big) Saved button on top-right (fixed)!
Now backup button is on bottom/left.
2.1
Now my_style.css and backup will be saved in content directory! (no more delete on upgrade)!
More other change in code…
2.0
Now use “$wp_filesystem->put_contents” and “wp_mkdir_p” instead of “file_put_contents” and “mkdir” (fix issue permission)…
Move backup in “hidden directory” – with old backup migration (prevent long css list in wordpress plugin editor)…
1.9
Add css stylesheets in backup management (just some little improvements)…!
Some fix in multisite network (disable view/erase backup except for blog_id 1)!
1.8
New important feature! Backup in setting panel (make backup when u click on save)!!! 😀
Now use “link” instead of @import (link improve performance!)…
1.6
Tested with wordpress 4.3.1
More code rewrite (fix for translator)!
Fix icon css issue.
1.5
New feture: Now is full compatible in network mode (multisite support)!
1.4
Fix a small issue in “@import url()” (add “;”) with safari browser!
1.3
Now code is saved both on database and also in file “my_style.css[+ ‘?filemtime’ to fix browser cache]” when you click on “Save” (made and updated via db+php only if is present css code). Thanks to this I can see custom css code in admin panel via database and put in source via file with ‘@import url(“my_style.css[+ ‘?filemtime’ to fix browser cache]”)’. I think (and hope) that this can optimize source code view and time load!
New “Save” button in plugin page (fixed via css in top right position)!
New “Top” button in bottom right position (classic “anchor” top button)!
I used this Plugin in +50 sites and the editor worked fine for years. Last Auto-Update to Version 3.3 crashed all my WP-Backends with several php-errors. No feedback from new developer. I deleted all my-custom-css-plugins and replaced them with another still supported css-editor-plugin.
I have used this plugin for years on many sites.
But I am not happy any more.
The last update (3.3) is bugged.
This plugin doesn't seem to be maintained any more seriously.
I will look now for an alternative. :-(
I had to disable the plugin. After that I was able to log in again. Now I have another editor installed.
It must be related to the last update.
What exactly about the error only knows the developer...
Used this for ages with no issues.. but a client site became inaccessible when we applied the latest update today so the server techs had a look and this was the issue:
[fcgid:warn] [pid 27640:tid xxxxxxxxxxxx] [client xxxxxxxxxxxxxx] mod_fcgid: stderr: PHP Parse error: syntax error, unexpected '[' in /var/www/vhosts/DOMAIN/httpdocs/wp-content/plugins/my-custom-css/my-custom-css.php on line 69
Had to disable the plungin to get back in the site but now can't access the custom CSS cide we put in this plugin for the site.
Is there any way to access the custom css site settings made via this plugin, before we have to do a full site restore to the previous backup.?
The update notice warns that this hasn't been tested with 5.1 (and PHP 7) so caveat emptor. It crashed my site with this error:
[Fri Mar 29 14:47:54.341135 2019] [:error] [pid 28028] [client 108.54.150.208:62513] PHP Parse error: syntax error, unexpected 'public' (T_PUBLIC) in /usr/local/webdocs/testsite/htdocs/wp-content/plugins/my-custom-css/pages/myphp/Edit.php on line 257
I use this plugin since many years and love it, because it saved my changes over all themes and WP updates. Ok, sometimes I have to include an !important so that the rule will be executed, but then it works perfect.
With the last updates, there are more options for searching and integrating code - I made the experience that this sometimes destroys the things I like to insert and I have to check it twice. Also with Firefox and Mac the command-button + F for searching doesn't work on the css-file in the edit-mode and the search inside the plugin doesn't work on my Mac (it finds the searched word and you can click on the up and down arrow, but the window doesn't jump to the point where I can find it. Possible that this is a Firefox problem - I didn't try it with another browser, because I don't like the other ones) - but my css-file isn't so long and most times I find what I am looking for. It only takes time...
Last time I discovered the backup function - the time before I worked with a second software for saving in the case the css doesn't work. But using the backup is much easier :)
All together I like to have one place where I can find my css - free from any theme or update. With this plugin I can manage this easily!
Hey man thanks a ton for this plugin it juist shopped off more than a second of loading itme from my website, seriously i didt expect switching to a better custom css plugin could have such a huge impact on performance. (I have spend alot of money on performance optimization and it didnt help as much as this).
