[Plugin: WP Super Cache] option descriptions are incomprehensible
option descriptions are incomprehensible.
Don’t cache pages for known users. (Logged in users and those that comment)
i can understand this this way: it mean don’t cache at all i.e. even do not use wp-cache for them. i think it can be needed to always show most correct content to them.
Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated. Recommended for very busy websites with lots of comments. Makes “directly cached pages” and “Lockdown mode” obsolete.
this is checked by default.
and i do not understand this.
why it is called “Cache rebuild”?
“Serve a supercache file to anonymous users while a new file is being generated.” hm. what is “a supercache file” that exists while “a new file is being generated” -> it is old version of file that is being generated -> the corresponding page content is just updated and for that the cache files (gz and html) are being updated, before they are ready, old versions are served to “guests”(“anonymous”). what happen if this is unchecked -> the files are somehow checked ie locked when content is updated and when they are requested by anonymous, they are not served, but page is generated with php. this is as i [can] understand it.
<q>Makes “directly cached pages” and “Lockdown mode” obsolete.</q> – why? and what does this mean? this like turns off “directly cached pages” and “Lockdown mode”? why? why directly cached pages cannot work with this option? i think they can (, as understand this option). why “Lockdown mode” cannot work? i think it can, and even this option itself can become then like not correct, so obsolte.
so maybe i understand this option not correctly.
Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!
hm. what is “Coarse file locking” and “usual” wp-super-cache locking? and when locking is used? when that file is updated?
List the newest cached pages (may be expensive to run on busy sites, use with caution.)
where to list? in dashboard?
Mobile device support.
it is unchecked. but i see “Mobile rewrite rules detected”. so, if rules are detected, why it ie support is unchecked? ahh.. rewrite rules are turning off cache for mobile devices. i understand this, but do not delete this paragraph, for some readers of this post.
6. “Garbage Collection” – what is this? i do not understand. why it is needed, what it does? is there garbage? how? i think there cannot be garbage ie incorrect, obsolete files because files are immediately updated (with usual and default configuration) when corresponding content is changed – new comment is made or post edited. also when post is deleted or made private, probably cache file is immediately deleted.
- The topic ‘[Plugin: WP Super Cache] option descriptions are incomprehensible’ is closed to new replies.