How do you avoid caching during development?

2 Views

Is there a simple way to prevent all caching when testing the appearance of changes to the site? I use WP Super Cache. I can delete its cache using the option provided, delete the cache for my browser, and still some changes to CSS or widgets do not refresh. I try other work-arounds like switching browsers or computers, but there must be a more stream-lined workflow where I can ensure I’m viewing the changes I made and not some cached earlier format? What’s the best solution for this?

Post Views: 2

Related posts

Leave a Reply

10 comments

  1. Add the filemtime() of your stylesheet as version parameter. Lets say, your default stylesheet is in css/default.css and css/default.min.css (not style.css). When we register a stylesheet on wp_loaded (not init), we can pass a version as fourth parameter. That will be the last modified time and therefore change every time we change the file.

    $min    = WP_DEBUG ? '': '.min';
$file   = "/css/default$min.css";
$url    = get_template_directory_uri() . $file;
$path   = get_template_directory() . $file;
$handle = get_stylesheet() . '-default';

// Overridden?
if ( is_child_theme() && is_readable( get_stylesheet_directory() . $file ) )
{
    $url  = get_stylesheet_directory_uri() . $file;
    $path = get_stylesheet_directory()     . $file;
}

$modified = filemtime( $path );

add_action( 'wp_loaded', function() use ( $handle, $url, $modified ) {
    wp_register_style( $handle, $url, [], $modified );
});

add_action( 'wp_enqueue_scripts', function() use ( $handle ) {
    wp_enqueue_style( $handle );
});

    If you are using Node.js and Grunt, I strongly recommend Browsersync. It will watch your files and update them instantly whenever they change. It can also synchronize the scrolling position, form submissions and more across multiple open browsers. Very cool.

  2. After searching for a simple solution many times i decided to find something that works!

    so… after thinking about it i found a great way to override caching while developing new websites… (and its easy).

    What we need is to tell wp this is a new CSS version like this…

    Before changes: 

    wp_enqueue_style( 'maincss', get_template_directory_uri() . '/css/style.css', array(), false, 'all' );

    After changes:

    wp_enqueue_style( 'maincss', get_template_directory_uri() . '/css/style.css?v='.time(), array(), false, 'all' );

    This is what we added:

    ?v='.time()

    Explanation:
    We are basically adding a dynamic version number to the css file which forces the browser to load the new css every time we update it.

    Don’t forget to remove it after your done developing otherwise your caching won’t work for this file and it would load for returning users again and again.

    This technique works for css & js files – hope this helps 😉

  3. This might seem overly simple, but how about just disabling caching until you’re done with the development portion of your site? It’s more than simple to turn on and off.

  4. I know that this question has had an answer accepted, but I think that that answer is still too complicated for the problem at hand, and may actually be incorrect depending on the user (no offense though), so I thought I’d still share how I bypass caching when I do my dev (not just with WordPress).

    Most modern browsers have something called incognito mode. In this mode, nothing in your computer is cached, so every refresh is a fresh slate download off the server. In Internet Explorer you press Ctrl + Shift + P. In Firefox and Chrome, you press Ctrl + Shift + N.

    If your browser doesn’t have incognito mode, you can normally force a hard reload by pressing Ctrl + F5 for IE, or Ctrl + Shift + R on Firefox and Chrome.

    As for your question regarding the CSS files (and essentially, all your asset files, like images and Javascript files), those aren’t cached in any way by WP Super Cache. Your settings and/or use of this plugin does not affect how those files are served. What’s caching those files are your browser, and that’s the reason why you do a hard reload.

    What the plugin does is it evaluates how WordPress builds your HTML files (via PHP), and stores a copy, so that the next time someone requests the same post, page, or whatever, it serves the copy, and won’t have to reevaluate the PHP-generated HTML again, and therefore save some computing time, loading your pages that much quicker. (I hope that’s clear.)

    The problem with that is, if you’re slapping on a timestamp on your CSS files’ URL via a PHP function, that is a PHP evaluation to HTML, and that will be cached by WP Super Cache. Every request to the same post will have the same timestamp because users are being served a copy of the original timestamp evaluation. (Correct me if I’m wrong.)

    The correct way to bypass WP Super Cache’s caching is to set the option Don't cache for known users to true in the plugin’s setting page.

    Finally (and this is a personal preference, as I’m a real stickler when it comes to coding), resorting to the use of incognito or forced hard reloads won’t require you to add unnecessary markup on your HTML pages. Of course, adding a timestamp only adds about 13 bytes per static file per request, but hey, like I said, I’m a stickler for this kind of stuff. It’s still 13 bytes unnecessary.

  5. What worked for me running WordPress on a Bitnami stack under Windows was to edit my php.ini file and restart my server.

    In the [opcache] section change the opcache.revalidate_freq to 1

    opcache.revalidate_freq=1

    I then restarted my servers and my pages now immediately show changes made to my plugins.

  6. Gosh, many ways to answer this one! First and foremost, you asked about two different things: WP Super Cache and CSS files. These are cached differently, in different places, so it’s important to recognize where your problem is.

    If WP Super Cache, you can define the constant DONOTCACHEPAGE in your functions.php during development to prevent WP Super Cache from caching anything. Don’t forget to remove this on launch though!

    define('DONOTCACHEPAGE', true);

    Each site also has a unique key to append to the URL to load a fresh version of the page, which you can find in the “Advanced” tab, I believe.

    Breaking it down to an even better solution, you should consider setting up a development environment and a production environment, where your development environment doesn’t have WP Super Cache enabled (again, assuming that’s your problem).

    If your issue is with CSS/JS files, then see the answer by toscho and subsequent comment by m0r7if3r above.

  8. If you’re using Chrome (which I highly suggest), open Inspector, click the settings icon in the lower right corner, and under “Network” select “Disable Cache.”