Stylesheet switching and caching

2 Views

I’m implementing a site that allows users to switch stylesheets (to show a high contrast version for people with vision impairments). The switcher essentially just changes the <link>ref to whichever stylesheet is appropriate.

However, I just realised that this will lead to problems when I switch on caching (either using WP Supercache or W3 Total Cache) – as only one version of the page will be cached and thus displayed to the user.

Read More

Any thoughts on possible solutions?

Post Views: 2

Related posts

Leave a Reply

3 comments

  1. I use W3TC, so these are approaches that I can come up with it for it:

    1. Fragment caching to exclude that part of page, will reduce cache effectiveness overall.

    2. Identify page with switched stylesheet by query argument, disable caching of such pages.

    3. Identify page with switched stylesheet by URL endpoint, disable caching of such by mask.

    4. Implement stylesheet switch via JavaScript (not really W3TC-specific).

  3. Turns out the answer is fairly simple (at least for WP Supercache).

    1. Use either PHP or legacy caching (ie not mod_rewrite)
    2. Turn on late init (either from the UI – recommended, or by setting $wp_super_cache_late_init = 1; in wp-content/wp-cache-config.php
    3. Use the <!--dynamic-cached-content--> directive to wrap the content that should remain dynamic.

    An example:

    <!--dynamic-cached-content--><?php
    display_high_contrast_link();
?><!--
   display_high_contrast_link();
--><!--/dynamic-cached-content-->

    As you can see, the dynamic content has been added twice – from the WP Supercache FAQ

    The first code is executed when the page is cached, while the second chunk of code is executed when the cached page is served to the next visitor.