Hi MicahBlu;
AO does a number of checks before kicking in (to ensure nothing gets badly broken);
if either
* wordpress’s is_feed() is true
* wordpress’s is_admin() is true
* there is no “<html” in the pge source
* there is “<xsl:stylesheet” in the page source
then AO does nothing.
My best guess; your theme’s header.php is lacking the opening HTML-tag?
hope this helps,
frank
HI Frank, thanks for the quick response. Unfortunately none of those conditions apply.
view-source:http://micahblu.com/
The plugin is currently active. The site is extremely simple and the only other plugin I have is SSH SFTP Updater Support, which I don’t think is conflicting with AO.. Any ideas?
verrrrrry weird …
some questions:
* you wouldn’t have output buffering disable in php.ini by any chance?
* can you check your phperror.log for any relevant entries?
* could you, ever so briefly, test with a default wordpress theme (twentyfifteen or -fourteen for example)?
frank
Changing the theme to twentyfifteen had no effect, I did however find an error in my log associated with AO:
[Mon Apr 20 12:19:01.572938 2015] [:error] [pid 20563] [client 108.23.119.50:56368] PHP Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /home/micahblu/htdocs/wp/wp-includes/update.php on line 295, referer: http://micahblu.com/wp/wp-admin/options-general.php?page=autoptimize&settings-updated=true
This may be due to the way I have my directories structured? I manage all my sites with git, composer, grunt, using composer to manage WordPress and its plugins as dependencies of my project, in order to achieve this the entire wordpress source is loaded in a wp directory from the root directory.
See https://github.com/micahblu/wp-launchpad
But I’m not sure how this would conflict?
Think I know what it is. Can write cache say no..
filesystem rights, indeed! ao needs to be able to write to wp-content/cache, if that is not the case then indeed nothing will happen.
frank
any luck changing the filesystem rights MicahBlu?
frank
