What about Preloading Super Cache file ?

From a question you asked elsewhere, I assume you are referring to the “v” parameter in WooCommerce query strings.

Short Answer:
As this plugin requires WPSC setting “Cache HTTP headers” to be checked, then it should still cache. However I don’t use WooCommerce (WC), and on my site requests with query strings are currently rewritten to slugs – it will be a few weeks before I can test/confirm. However whatever solution (below) you use with WC will have drawbacks.

Long Answer:

From WC docs it appears that the “v” parameter is set when you enable WC’s “Geolocate with page caching support” option. In reality it is a cache buster and on for most sites does the opposite! A better label would “Disable caching – but still let my site waste time running a caching plugin” .

Option 1.

Likely to be faster and more efficient. Use Country Caching Extension and change your WC settings to switch off “Geolocate with page caching support”. Unfortunately this also switches off geolocation by Ajax.

Issues: This might be fine if you are only selling in say Europe, Russia and UK but probably no good when also selling in US as different states have different taxes (a page cached as US due to a visitor from Texas might be wrong for later visitor from NYC).

Option 2.

This plugin should work with the “v” query string, however if your site is WC (ecommerce) ONLY then it is probably unnecessary. Apparently the “v” parameter translates to a location e.g. Alabama, US. If your site is WC (ecommerce) ONLY then you might as well just use WPSC (with “HTTP header” option) or other query string capable cache plugin.

Issues: If your site has only a few thousand visits per day the benefits of caching may end up negligible or even negative. e.g. You may only get single visitors from many locations; as your site has to check for cache and then create one before sending the page – response will actually be slower.

It will also result in a horrific exponential increase in the number of cache files stored by your server, at some point this could also cause performance issues. n.b. the increase would be the same whether using just WPSC or WPSC with Country Caching just cache suffix would be different e.g. “v123” or “UK-v123” as v123 is always UK.

Option 3.

Deactivate caching. May be the best option if response times still okay.

I have no experience of WooCommerce so there may be other issues/solutions I am unaware of. In my view WooCommerce would be improved if it provided an additional option to cache and use Ajax. Or maybe an (if country caching) allow cache except user specified list of country codes e.g. “US,XX,YY” to cover issues of regional taxes (and shipping costs?) etc.

Unfortunately your question was unclear. On checking questions you asked elsewhere I assumed you were inappropriately using the term “preload” to simply mean creating a cache “snapshot” on first request that would be served to later visitors. As I’ve not had a response I assume my assumption was correct.

For others wanting to know about preload (as described by WPSC) and advance creation of cache files for all possible “v” values; then the answer is NO, neither WPSC nor this plugin will do this.

N.B. The “v parameter” identifies visitor location at below Country level e.g. US state. So “v param” pre-loading (if possible) would result in the creation of about 300 FILES (cached snapshot pages) for EACH PAGE! (More if visitors outside the US are also identified at below country level).

• This reply was modified 6 years, 7 months ago by wrigs1.

Question answered, and no response. Marking as resolved.