Title: Installing a HTTPS caching plugin before finalised design.
Last modified: May 30, 2017

---

# Installing a HTTPS caching plugin before finalised design.

 *  [UserUser](https://wordpress.org/support/users/rizwaanakhtar91/)
 * (@rizwaanakhtar91)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/installing-a-https-caching-plugin-before-finalised-design/)
 * _[ Moderator note: [moved to Fixing WordPress](https://wordpress.org/support/topic/before-posting-in-everything-wordpress/?view=all).]_
 * Hi Guys,
 * I’m working on a website at the moment; I’ve created the site pages (which are
   live), but it I’m still modifying and updating the layout, images, and content.
 * I need to install a plugin which caches the site and makes the pages in a static
   html file, however I’ve read that once I install a caching plugin it won’t allow
   me to modify and update the site pages; as the plugins stores a version of the
   pages to the server.
 * I just want clarity on what I can and cannot do once I install a cachcing plugin,
   and how I should proceed. I’m thinking of finalising the pages (could take a 
   few weeks) and then installing the plugin. But if I can install a plugin that
   allows me to keep making modifications, I would do that instead.
 * Thank you!

Viewing 1 replies (of 1 total)

 *  Moderator [tobifjellner (Tor-Bjorn “Tobi” Fjellner)](https://wordpress.org/support/users/tobifjellner/)
 * (@tobifjellner)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/installing-a-https-caching-plugin-before-finalised-design/#post-9179433)
 * There are different types of cache.
    You should, certainly, use server cache:
   If someone requests a page that has recently been built, then the already composed
   html page will be sent to the visitor, without the server having to read and 
   run a large number of php files and saving a big number of database requests.
   Whenever you update a page, the cache will be rebuilt. In most cases, there will
   also be a special admin button `purge cache`, which is good to use whenever you’ve
   changed anything important on the site (layout, widgets, etc.)
 * Then there’s browser cache: The server may send information together with served
   files, saying that “This file may be stored locally for reuse later”. This is
   good for files that don’t change. Could be images. Could be javascript libraries(
   where any change would actually also have a new version number, thus resulting
   in a different URL). This type of caching shouldn’t be used (at least not with
   a long “best-before-date” for files that you may change from time to time).
 * There’s more to cacheing than this. But if you grasp this much, then you’ll be
   on the right way.

Viewing 1 replies (of 1 total)

The topic ‘Installing a HTTPS caching plugin before finalised design.’ is closed
to new replies.

## Tags

 * [caching](https://wordpress.org/support/topic-tag/caching/)
 * [HTTPS](https://wordpress.org/support/topic-tag/https/)
 * [static html](https://wordpress.org/support/topic-tag/static-html/)

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 1 reply
 * 2 participants
 * Last reply from: [tobifjellner (Tor-Bjorn “Tobi” Fjellner)](https://wordpress.org/support/users/tobifjellner/)
 * Last activity: [8 years, 10 months ago](https://wordpress.org/support/topic/installing-a-https-caching-plugin-before-finalised-design/#post-9179433)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics