Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Description of Caching Types #224
I want to change the descriptions and even names of the different caching types to make it easier for new users to understand what settings they should use. At present we have:
This exposes the implementation of the caching delivery, not what they're useful for. A technical user might understand the implications of the first two but not the third. Any other user will be lost but at least the settings page recommends PHP mode.
Related to legacy caching is the option "Don’t cache pages for known users." which is recommended. This disables a portion of legacy page caching. That stops caching when logged in users or users who comment visit the site, except for feeds because of this code.
There's also "Don’t cache pages with GET parameters" which disables the other function of legacy caching which is to cache pages that have ?x=y or whatever at the end of the URL.
Methods 1 and 2 are used only to store hits from anonymous, unknown users. Legacy caching is always used (except when the options above are selected) to cache files for known users like those that are logged in or leave comments.
With the changes to legacy caching I feel more confident about people using it more. It should be used to cache REST API calls for example.
So what should we call them?
Maybe separate them out to "anonymous users" and "full caching" groups?
One thing to consider is that legacy caching always works anyway unless deliberately disabled so maybe we should only ask the user to choose between the first two caching methods, and offer options to disable caching for known users and the GET parameters..
I am by no means beginner in WP and this with "known users" is a bit confusing. What is an "known User" ?
I noticed it does not (sometimes) serve cached page when User logout. With message:
Is it browser cookie dependent ? Confusing.