=== Simple Custom CSS and JS === Created: 06/12/2015 Contributors: diana_burduja Email: diana@burduja.eu Tags: CSS, JS, javascript, custom CSS, custom JS, custom style, site css, add style, customize theme, custom code, external css, css3, style, styles, stylesheet, theme, editor, design, admin Requires at least: 3.0.1 Tested up to: 5.9 Stable tag: 3.38 License: GPLv3 License URI: http://www.gnu.org/licenses/gpl-3.0.html Requires PHP: 5.2.4 Easily add Custom CSS or JS to your website with an awesome editor. == Description == Customize your WordPress site's appearance by easily adding custom CSS and JS code without even having to modify your theme or plugin files. This is perfect for adding custom CSS tweaks to your site. = Features = * **Text editor** with syntax highlighting * Print the code **inline** or included into an **external file** * Print the code in the **header** or the **footer** * Add CSS or JS to the **frontend** or the **admin side** * Add as many codes as you want * Keep your changes also when you change the theme == Installation == * From the WP admin panel, click "Plugins" -> "Add new". * In the browser input box, type "Simple Custom CSS and JS". * Select the "Simple Custom CSS and JS" plugin and click "Install". * Activate the plugin. OR... * Download the plugin from this page. * Save the .zip file to a location on your computer. * Open the WP admin panel, and click "Plugins" -> "Add new". * Click "upload".. then browse to the .zip file downloaded from this page. * Click "Install".. and then "Activate plugin". OR... * Download the plugin from this page. * Extract the .zip file to a location on your computer. * Use either FTP or your hosts cPanel to gain access to your website file directories. * Browse to the `wp-content/plugins` directory. * Upload the extracted `custom-css-js` folder to this directory location. * Open the WP admin panel.. click the "Plugins" page.. and click "Activate" under the newly added "Simple Custom CSS and JS" plugin. == Frequently Asked Questions == = What if I want to add multiple external CSS codes? = If you write multiple codes of the same type (for example: two external CSS codes), then all of them will be printed one after another = Will this plugin affect the loading time? = When you click the `Save` button the codes will be cached in files, so there are no tedious database queries. = Does the plugin modify the code I write in the editor? = No, the code is printed exactly as in the editor. It is not modified/checked/validated in any way. You take the full responsability for what is written in there. = My code doesn't show on the website = Try one of the following: 1. If you are using any caching plugin (like "W3 Total Cache" or "WP Fastest Cache"), then don't forget to delete the cache before seing the code printed on the website. 2. Make sure the code is in **Published** state (not **Draft** or **in Trash**). 3. Check if the `wp-content/uploads/custom-css-js` folder exists and is writable = Does it work with a Multisite Network? = Yes. = What if I change the theme? = The CSS and JS are independent of the theme and they will persist through a theme change. This is particularly useful if you apply CSS and JS for modifying a plugin's output. = Can I use a CSS preprocesor like LESS or Sass? = For the moment only plain CSS is supported, but you can check out the [Pro version](https://www.silkypress.com/simple-custom-css-js-pro/?utm_source=wordpress&utm_campaign=ccj_free&utm_medium=banner) in case you need a CSS preprocessor. = Can I upload images for use with my CSS? = Yes. You can upload an image to your Media Library, then refer to it by its direct URL from within the CSS stylesheet. For example: `div#content { background-image: url('http://example.com/wp-content/uploads/2015/12/image.jpg'); }` = Can I use CSS rules like @import and @font-face? = Yes. = Who can publish/edit/delete Custom Codes? = By default only the Administrator will be able to publish/edit/delete Custom Codes. On the plugin activation there is a role created called Web Designer. You can assign this role to a non-admin user in order to allow to publish/edit/delete Custom Codes. On the plugin's Settings page there is an option to remove this role. = Compatibility with qTranslate X plugin = * If the [qTranslate X](https://wordpress.org/plugins/qtranslate-x/) plugin is adding some `[:]` or `[:en]` characters to your code, then you need to remove the `custom-css-js` post type from the qTranslate settings. Check out [this screenshot](https://www.silkypress.com/wp-content/uploads/2016/08/ccj_qtranslate_compatibility.png) on how to do that. = My website has HTTPS urls, but the codes are linked as HTTP = The URL for the linked Codes is built just like the URL for other media (from Media Library) by using the WordPress Address option found on the WP Admin -> Settings -> General page, as shown in [this screenshot](https://www.silkypress.com/wp-content/uploads/2016/12/ccj-siteurl.png). If the WordPress Address has HTTPS in the url, then the Custom Codes and all the other media will have HTTPS in the url. == Screenshots == 1. Manage Custom Codes 2. Add/Edit Javascript 3. Add/Edit CSS $. Add/Edit HTML == Changelog == = 3.38 = * Fix: compatibility with the `HTML Editor Syntax Highlighter` plugin * Fix: escape labels on the "Add new custom code" page * Feature: Keep the last cursor position in the editor and let the editor get focus when the page loads = 3.37 = * 07/12/2021 * Fix: allow the TablePress plugin to load its JS files on the "Add custom code" page in admin * Feature: highlight active line in the editor * Feature: add "Ctrl + J" shortcut to the editor for jumping to the matching tag = 3.36 = * 02/23/2021 * Fix: fatal error with PHP8.0 = 3.35 = * 01/19/2021 * Tweak: change dummy revision dates to fictional dates before 2000 * Fix: replace the deprecated postL10n JS object with wp.i18n * Fix: add "tipsy-no-html" to the tooltips on the settings page = 3.34.1 = * 11/24/2020 * Fix: PHP error when filtering the custom codes = 3.34 = * 11/01/2020 * Feature: enqueue the jQuery library if one of the JS custom codes requires it * Fix: set cookie SameSite attribute to lax = 3.33 = * 08/20/2020 * Fix: the user language preferrence was ignored in favor of the site defined language * Fix: allow the jQuery library added by plugins like Enable jQuery Migrate Helper or Test jQuery Updates * Fix: permalink was not editable with WordPress 5.5 * Feature: fullscreen editor * Feature: button for beautifying the code = 3.32.3 = * 08/02/2020 * Fix: add "Cmd + " editor shortcuts for MacOS computers = 3.32.2 = * 07/14/2020 * Fix: use file_get_contents instead of include_once to load the custom codes = 3.32 = * 07/08/2020 * Fix: compatibility issue with the Product Slider for WooCommerce by ShapedPlugin * Feature: "Ctrl + /" in the editor will comment out the code * Feature: order custom codes table by "type" and "active" state * Feature: autocomplete in the editor = 3.31.1 = * 05/05/2020 * Declare compatibility WooCommerce 4.1 = 3.31 = * 03/21/2020 * Feature: add "After tag" option for HTML codes, if the theme allows it * Feature: don't show type attribute for script and style tags if the theme adds html5 support for it * Code refactory * Fix: the permalink was mistakingly showing a ".css" file extension when being edited = 3.30 = * 03/12/2020 * Feature: color the matching brackets in the editor * Declare compatibility WooCommerce 4.0 * Declare compatibility WordPress 5.4 = 3.29 = * 01/31/2020 * Fix: date Published and Modified date wasn't shown in Japanese * Feature: indentation in the editor * Feature: close brackets in the editor = 3.28 = * 11/05/2019 * Tweak: update the Bootstrap and jQuery library links * Declare compatibility with WordPress 5.3 = 3.27 = * 08/08/2019 * Compatibility with the "CMSMasters Content Composer" plugin * Feature: keep the cursor position after saving * Option: remove the comments from the HTML = 3.26 = * 05/08/2019 * Fix: remove the Codemirror library added from WP Core * Tweak: use protocol relative urls for custom code linked file * Declare compatibility with WordPress 5.2 = 3.25 = * 04/21/2019 * Tweak: update the Bootstrap and jQuery library links * Declare compatibility with WooCommerce 3.6 = 3.24 = * 04/05/2019 * Fix: remove the editor scrollbar * Tweak: rename "First Page" to "Homepage" to avoid misunderstandings = 3.23 = * 03/15/2019 * Fix: avoid conflicts with other plugins that use CodeMirror as their editor = 3.22 = * 12/06/2018 * Fix: another solution for the bug related to the Edit Custom Code page was blank for WordPress 5.0 and the Classic Editor enabled = 3.21 = * 12/06/2018 * Fix: the Edit Custom Code page was blank for WordPress 5.0 and the Classic Editor enabled = 3.20 = * 11/15/2018 * Fix: remove compatibility with the Shortcoder plugin. Bug https://wordpress.org/support/topic/edit-page-blank-8/ * Declare compatibility WooCommerce 3.5 = 3.19 = * 10/16/2018 * Fix: keep the editor LTR even on RTL websites * Fix: flush rewrite rules after modifying the "Add Web Designer role" option = 3.18 = * 07/13/2018 * Fix: the default comment for JS for other locales than "en_" was removing the tags * Tweak: make the search dialog persistent * Tweak: correct the tooltip info for the 'ccs_js_designer' option = 3.17 = * 04/25/2018 * Fix: add the add/edit/delete custom post capabilities to the admin and 'css_js_designer' roles on plugin activation = 3.16 = * 04/22/2018 * Fix: "The link you followed has expired" on custom code save if the WP Quads Pro plugin is active * Fix: PHP warning for PHP 7.2 * Change: add/remove the "Web Designer" role only on activating/deactivating the option in the Settings page = 3.15 = * 03/27/2018 * Change: check the option name against an array of allowed values = 3.14 = * 02/04/2018 * Feature: permalink slug for custom codes * Fix: set the footer scripts to a higher priority * Update the french translation * Fix: allow admin stylesheets from ACF plugin, otherwise it breaks the post.php page * Tweak: for post.php and post-new.php page show code's title in the page title = 3.13 = * 01/12/2018 * Feature: add the "Keep the HTML entities, don't convert to its character" option = 3.12 = * 01/03/2018 * Reverse to the `wp_footer` function for the footer scripts, as the `print_footer_scripts` function is used also in the admin, which lead to many broken back-ends = 3.11 = * 01/03/2018 * Use the `print_footer_scripts` function for the footer scripts (https://wordpress.org/support/topic/footer-code-position-before-external-scripts-is-overridden/) * Escape selectively the HTML characters in the editor (https://wordpress.org/support/topic/annoying-bug-in-text-editor/) = 3.10 = * 12/15/2017 * Fix: https://wordpress.org/support/topic/broken-layout-of-code-snippet-type-color-tag-css-html-js-on-main-list-table/ * Feature: add filter by code type * Feature: make the 'Modified' column sortable * Fix: if the default comment remains in the "Add Custom JS", then there was no