Known Issues
Whilst it tries to be a plug-and-play solution PHP Speedy can't (yet) do everything. The following are some issues you should take into account if you are having problems:- The config.php file and the cache directory must be writable by the server
- PHP Speedy doesn't compress external JavaScript or CSS files. This means your widgets, tracking codes etc will not be compressed
- PHP Speedy ignores JavaScript of CSS served with any extension other than .js or .css. This is because if the extension is .php or something else, the file is probably dynamic and therefore probably shouldn't be cached
- If you have a JavaScript that loads other JavaScripts via document.write this may cause problems. The new scripts will be loaded after the entire block of all your other scripts, thereby changing the load order. In this case, you should manually link to each script individually.
- PHP Speedy ignores querystrings in the links to your JS and CSS files
- PHP Speedy only sets the expiration for your CSS and JS files. It doesn't (yet) handle the images, which is probably why you won't score an A in Y-Slow for far future expires.
- In Wordpress MU, you cannot configure your MU sites for PHP Speedy individually; the same config affects all the sites you have enabled PHP Speedy on. This is a feature (not a bug). You should also turn off PHP Speedy file cleanup if using MU.
- PHP Speedy doesn't support the @import syntax for including CSS files
- Don't forget to activate PHP Speedy once you have tested the configuration!
PHP Speedy Configuration
