Back to Community

Troubleshooting CSS and JS Files Not Updating in Simple Custom CSS and JS

48 threads Sep 16, 2025 PluginSimple custom css and js

Content

If you've made changes to your custom CSS or JS code in the Simple Custom CSS and JS plugin, but those changes aren't appearing on your live website, you're not alone. This is a common issue often related to caching. This guide will explain why it happens and walk you through the most effective solutions.

Why Don't My Changes Appear Immediately?

The plugin is designed to update your site's frontend automatically. When you save a change, it creates a new file in the /wp-content/uploads/custom-css-js/ directory and uses a "cache-busting" technique. This means it adds a unique query string to the file URL (e.g., style.css?ver=123), which should force visitors' browsers to load the new version instead of a cached one.

However, several factors can interfere with this process:

  • Aggressive Caching Plugins: Performance plugins (e.g., W3 Total Cache, WP Super Cache) can heavily cache static files like CSS and JS.
  • Server-Level Caching: Your web host may employ its own server-side caching mechanisms.
  • CDN Caching: Content Delivery Networks (CDNs) like Cloudflare serve static files from their own global networks.
  • Browser Cache: Your local browser may be holding onto an old version of the file.

How to Fix It: Step-by-Step Solutions

1. Clear All Caches

This is the most common and effective first step. You must clear every cache between your plugin and the visitor.

  • WordPress Caching Plugins: Locate the "Purge All Caches" or similar button in your caching plugin's settings (e.g., in W3 Total Cache).
  • CDN Cache: If you use Cloudflare or another CDN, log into its dashboard and find the option to purge the cache.
  • Server Cache: Some hosting providers have a caching system in their control panel (e.g., LiteSpeed Cache). Check your host's documentation or support pages for how to clear it.
  • Browser Cache: Do a "hard refresh" on your site by pressing Ctrl + F5 (Windows) or Cmd + Shift + R (Mac).

2. Manually Regenerate the Cache Files

Sometimes, the physical cache file in the uploads folder may not generate correctly. You can force the plugin to recreate it:

  1. Go to WP Admin -> Custom CSS & JS.
  2. Open each custom code you have edited for editing.
  3. Simply click the Update or Save button. This action regenerates the external file.

3. Check Your WordPress Address Settings

The plugin constructs the URL to external CSS/JS files based on your site's WordPress Address. If this is incorrect, it can cause issues, especially with HTTPS.

  1. Go to Settings -> General.
  2. Ensure both the WordPress Address (URL) and Site Address (URL) are identical and start with https:// if your site uses SSL.

4. Verify the Files Are Loading

To confirm whether your new code is even being output by the plugin, view your website's page source.

  1. Right-click on your webpage and select View Page Source.
  2. Press Ctrl + F (Windows) or Cmd + F (Mac) and search for a unique word or selector from your custom CSS code.
  3. If you find it, the code is being output correctly, and the issue is purely visual due to caching. If you cannot find it, there may be a deeper problem with the plugin's configuration.

When All Else Fails

If you continue to experience problems after following these steps, consider these factors:

  • Multisite Networks: The plugin can sometimes behave differently on WordPress Multisite installations. Try disabling and re-enabling the specific custom code on the affected site.
  • File Permissions: In rare cases, the web server may not have write permissions to the /wp-content/uploads/custom-css-js/ folder, preventing it from creating new files. The required permission is usually 755, not 777.

By methodically working through these solutions, you should be able to resolve most issues related to CSS and JS updates not appearing on your site.

Related Support Threads Support