This article is about caching on your WordPress Hosting package, and these features are not available within Professional Hosting and Business Hosting packages.
Your WordPress Hosting package makes use of caching to improve performance of your site. By default we have 3 separate caching tools which help to make your site feel fast for your users.
Caching works by storing pre-generated objects, for example with Nginx Fast-CGI cache, the entire output of a post or page from WordPress is stored. From time to time the cache may look to see if the page/Post has change which means that if you make changes to posts or pages and have full page caching enabled, those changes won't immediately be visible if you are not logged in.
This is not normally an issue, in most cases you will be logged in and once the caches are updated everyone will see the new content.
If you are developing a site or if you are trying to solve an issue a visitor on your site has reported, then you might want to turn off one or more caching methods.
Manage Your Caches
You can manage your Nginx & mod_pagespeed caches via the 34SP.com tools Plugin within your site’s WordPress admin area. This plugin is activated by default on all accounts.
Within the admin area menu click Tools > 34SP.com Developer Tools
Nginx Fast-CGI cache has 3 options, disabling Nginx and mod_pagespeed cache entirely, purging the cache by URL, or purging the cache of all URLS.
Disabling Nginx Fast-CGI cache
Within the 34SP.com Developer Tools, the current status of your Fast-CGI cache should be showing, normally this is enabled or disabled.
When disabled, requests made to the server are handled directly by Nginx and PHP-FPM rather than the Nginx Fast-CGI cache.
To enable/disable the cache click on the 'Enable Nginx Cache or 'Disable Nginx Cache' buttons. Please note this will take a few seconds to process.
Once done, the status of Nginx Fast-CGI cache will change.
Purging or flushing the cache sounds drastic, but simply means telling Fast-CGI to remove content which has been cached so that the next time that content is requested a fresh copy is generated and then stored in the cache.
Flushing the cache is useful when content is not showing for non logged in users. To flush the cache, simply click 'Clear Cache'.
Note that the cache will only be flushed if Fast-CGI cache is enabled.
CloudFlare is a third party service, which provides a range of features to help improve your site, including performance benefits through caching.
CloudFlare can be turned on or off within your 34SP.com Control Panel.
Temporarily Disabling CloudFlare
If you are making lots of changes to your site then you may wish to bypass CloudFlare for a limited period (disabling and re-enabling CloudFlare normally involves some waiting). You can do so by using the CloudFlare "Developer Mode". In this mode requests are passed straight through CloudFlare servers to your site.
Within your 34SP.com Account:
Select CloudFlare > Developer Mode and click the button labelled Enable Developer Mode
Purging Cloudflare Caches
Through the 34SP.com Control Panel you can purge/flush caches.
Within Your 34SP.com Account:
Select CloudFlare > Cache Control and click Clear Entire Cache
To flush individual URLs, you can specify each url in the format /my-url-to-purge/ in the box URLs to clear. Then click the button labelled Purge CloudFlare URLs.
Please note: Pages refers to the generated content stored by CloudFlare and can be a post, page, category or any WordPress generated URL.
Disabling CloudFlare Entirely
Disabling or enabling CloudFlare permanently can only be done through the 34SP.com Control Panel.
Because CloudFlare sits in front of your site, turning CloudFlare involves updating nameservers. If your DNS is pointing to 34SP.com nameservers this is a one click process.
To enable/disable CloudFlare within 34SP.com account panel select Cloudflare. For each address of your site (normally www and non www) select if you wish to have CloudFlare enabled, then click Update Nameservers button. There maybe a short delay while these changes take effect.