Some of my observations and suggestions
-
Hi,
the Gator Cache is a great plugin, the only one that works as expected, is multisite compatible and is not over-complicated as WP Super Cache or W3TC.
After a while I have found some issues or quirks which makes it a little bit less perfect. But some of them might be just my misunderstandings. So here they are:- Cached feeds are served with wrong Content Type header text/html.
Probably not a big issue but some feed parsers might have difficulties to read them.
A quick fix is to put this rewrite rule in .htaccess:
RewriteRule /(comments/)?feed - [T=text/xml]
But better solution would be to save the cached index file with .xml extension. - Pages without trailing slash are always served by PHP.
On sites with no trailing slash in permalink structure the URL like /page is served by Advanced Cache while URL like /page/ is served correctly from a cached file.
This is apparently caused by incomplete .htaccess rewrite rules which don’t take the missing trailing slash into account and by that they are simply skipped and then served by PHP. - List of subsites in .htaccess rules are wrong.
There is a bug in getHostString() method that generates list of allowed hosts for Apache rewrite rules in multisite (subdomain) configuration. There is listed only the main domain name for each site. - Apache rules for handling of cached files should be defined only for the cache directory.
The first part of the main .htaccess file that deals with serving of cached and compressed files should be moved to .htaccess file in the cache directory. Otherwise it will badly influence the serving of any .gz file in uploads or wp-content folder. Only rewrite rules should be left in the main .htaccess file. - Gzip compression should be switchable in the UI.
Even though it is currently switchable directly in config.ini file, there should be switch also in the UI. Many servers are already compressing html files on the fly and removing unnecessary Apache configs will simplify many things. - Better placement for cache directory and configs.
As someone else in the support forum suggested, the default location for cache directory should be in wp-content/cache (or under) and config.ini files also in wp-content. It’s more standardized way of organizing files in WP. - Cache Warming should be deferred for later run.
Cache Warming is a pretty neat feature but in some cases it’s very intensive operation and it slows down the post publishing and editing. I haven’t look in the code how it’s done but scheduling it via wp-cron for later run would be very useful.
I hope my suggestions would make your plugin even more better ??
Petr
- Cached feeds are served with wrong Content Type header text/html.
Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
- The topic ‘Some of my observations and suggestions’ is closed to new replies.