Important note

This tutorial assumes you have already created a Pull Zone.

Installing WP Super Cache

  1. Log into your WordPress admin panel
  2. Hover your mouse over “Plugins” and click “Add New”
  3. In the “Search” box, type “WP Super Cache” and click “Search Plugins”
  4. The first option will be “WP Super Cache” and in the “Description” box, it will show that the plugin is created by “Donncha O Caoimh”. This is the plugin you need to install.
  5. Click “Install Now”. A prompt dialog will open and ask if you are sure you want to install the plugin, click “OK.” After the plugin is installed, click “Activate Plugin”.
  6. You should see a yellow box advising, “WP Super Cache is disabled. Please go to the plugin admin page to enable caching.” Click on the “plugin admin page” to go to the settings page.
  7. The settings for “WP Super Cache” can be found under the “Settings” menu in the WordPress admin dashboard

    There! Now you are ready to configure the plugin’s options.

Configuring WP Super Cache

  1. Log into your WordPress admin panel, scroll down to the “Settings” link on the left panel, and click on “WP Super Cache”
  2. The first tab is called “Easy”. Ticking the “Caching On” option and then clicking “Update Status” is all that needs to be done on that page.
  3. Next step is to click on “Advanced”, and start setting the options that best fit your blog. We have listed the recommended settings below, but of course the best settings for your blog may be different.
    1. Tick the “Cache hits to this website for quick access.” check box next to “Caching.” (Recommended)
    2. Tick the “Use mod_rewrite to serve cache files.” radio box. (Recommended)
    3. Under “Miscellaneous“, make sure to tick the check boxes next to the following options:
      • Compress pages so they’re served more quickly to visitors. (Recommended)
      • Don’t cache pages for known users. (Recommended)
      • Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated. (Recommended)
    4. Important note

      If you should need “304 caching,” make sure to use the php caching method as it can’t work side by side with mod_rewrite. Also, the php method has a performance advantage compared to legacy mode.

    5. You can leave the rest of the option as they are, no changes.
    6. Click “Update Status”
    7. After that, you may get a message asking you to “Update Mod_Rewrite Rules,” so scroll down the page until you find that option, and then click the button
  4. Now click the ” CDN” tab.
  5. Tick the “Enable CDN Support” check box.
  6. In the box next to “Off-site url” box, enter your CDN URL prefixed with http://. You can use the Temporary CDN URL which you have been given after you have created your Pull Zone. If you are using a Custom Domain, such as cdn.mysite.com, you can input that in the text box.
  7. Insert the same URL in the box next to “Additional CNAMES”
  8. Tick the check box called “Skip https URLs to avoid “mixed content” errors” — this will prevent any SSL errors if you have some parts of your website under SSL. Enable this option only if you do not have a Custom or Shared SSL CDN URL.
  9. All done. Click “Save Changes.”
  10. Not always necessary, but you can click on “Contents” and “Delete Cache” to make sure the cached contents of WP Super Cache contents is fresh.

NOTE

To ensure you implemented MaxCDN correctly, you can view the source code of any page to confirm that the CDN domain is being used for static assets instead of your origin domain. You can also use tools like pingdom, gtmetrix, webpagetest that can give you more detailed reports on your CDN implementation status.

  • DaveyJake

    Steps 3B & 3C say to use “mod_rewrite” and “304 Browser Not Modified caching.” The only issue is in WP Super Cache, it states, “Warning! 304 browser caching is only supported when not using mod_rewrite caching.” Thoughts?

    • Ivan Dabic

      Hey DaveJake! You are right, this has been the case since version 1.1. so, I’ll get this updated as soon as possible. Thanks for noticing it.
      As for the actual setting I’d recommend skipping 304 in favor of mod_rewrite caching because it takes the lead against php or legacy caching. If this is, however, something you can’t afford (304 is mandatory) you should choose php instead.

  • http://www.gaminglaptopsjunky.com/ Junky

    But how files will be loaded to the CDN? Supercache does it automatically?

    • Marko Markovic

      Hey there! In case of the Pull Zone with MaxCDN you just need to go through this guide which will rewrite your static assets (images, js, css, video and audio) with CDN domain. Your visitors will then request static assets through MaxCDN network where a particular asset gets cached on CDN server when two requests are made to it.

      If you are interested in how to manage the expiry of the files you can review the following articles:

      -Manage Expiry in MaxCDN Control Panel (Ignore Cache Control section): https://www.maxcdn.com/blog/edge-settings/
      -Manage Expiry on Origin Server: https://www.maxcdn.com/one/tutorial/custom-expiry-headers/

      If you have any other questions please feel free to send us an e-mail to support@maxcdn.com

  • http://aftercredits.com/ AfterCredits

    Anyone else getting blank pages after enabling CDN in SuperCache? I’ve checked, double-checked, etc., but can’t figure out why!

    I just moved hosting, from shared to AWS, and am now running a LEMP stack. Maybe that has something to do with it?

    • http://www.maxcdn.com/ Petar Petrovic

      Hello,

      That looks like the issue on your origin server. I suggest checking your PHP & nginx configuration, as well as the corresponding error logs. Also, checking out the errors in the console (if any) of your web browser might also give you a hint at what might be going wrong.

    • Ivan Dabic

      Interesting. Would you send us details on support@maxcdn.com ? It can happen due to corrupted page cache or minified css/js. Additionally, if you changed the origin server, plese make sure to update the origin ip in MaxCDN CP:

      https://www.maxcdn.com/one/tutorial/update-origin-ip/

      Keep us posted, please.

      • http://aftercredits.com/ AfterCredits

        Thanks, email sent. I believe I am using nginx’s minify settings. Perhaps that’s the culprit.