LiamE

What does it have to do with this plugin?!

Pay for it and you get support, what do you expect?!

Yes that’s fine, just make sure you use the correct paths when you go live.

How were you planning to migrate from local to live?

2.3.3
Release Date: August 6th, 2015

Removes the autocomplete functionality from the focus keyword field in the Yoast SEO metabox because Google is shutting down its autocomplete API as of August 10th.

2.3.3
Release Date: August 6th, 2015

Removes the autocomplete functionality from the focus keyword field in the Yoast SEO metabox because Google is shutting down its autocomplete API as of August 10th.

It is horrible indeed, why add that stupid bloat to 20% of the internet? If I want emojis I either create or install a plugin.

The only and most horrible decision by WP.

But you already know if user is using separate theme for mobile users – they have “Create cache for mobile theme” ticked in the settings ?? For everyone else it’s not necessary…

Take care and keep up the good work, really good plugin otherwise! It was just a suggestion not an attack.

@bryan Stringer – Most likely it doesn’t work because it’s using PHP to register the hits. This is the main principle how caching works, it doesn’t let visitors hit your php processes all the time and serves them static content (which you can delete also) – this is what make the site faster and let’s it work under big load.

The only solution is to use something that is using javascript/ajax requests to log the hits, I don’t know which plugins do that or if it’s possible with the one you’re using.

@emre You should – Probably make a sticky + add the information to your FAQ, majority of the “problems” are here similar, people just don’t understand the core principle of caching… ?? maybe you can reduce by that way the same questions all over again and again.

https://checkgzipcompression.com/

Use this to see if your file(s) are gzipped, firebug file size doesn’t matter, your browser is unpacking the files for you anyway.

You can buy his pro version to show support ?? even if you don’t need the features.

It’s a free plugin, what are you yelling at? If you want support – pay for it.

I am aware of the redirect loop fix, that was not the problem.

The problem is why the homepage is served with php, not with mod_rewrite…

The one in your root path, most likely www/.htaccess

Make sure you have something along these lines already inside the htaccess file:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

Make it writable and after enabling the WP Fastest Cache, make sure you put the same access rights back.

And if I turn off “Make known users anonymous so they’re served supercached static files.” since PHP is removing the cookies and it get hit before mod_rewrite (?) still PHP is serving the files… I opened an incognito window and log tells me:

supercache dir: /var/www/xxx.com/wp-content/cache/supercache/www.xxx.com/Fetched static page data from supercache file using PHP. File: /var/www/xxx.com/wp-content/cache/supercache/www.xxx.com/index-https.html