WordPress 3.5 and mod_pagespeed do NOT play well together
If none of the URLs contain the word “pagespeed” then it probably isn’t turned on. What if it is? How does one fix it?
Option #1 —
a2dismod pagespeed && service apache restart
WordPress suggests that you simply disable mod_pagepseed. That’s the simple solution and that did fix my button/dropdown issues. However, that sort of sucks since mod_pagespeed has, otherwise, been serving me faithfully. This also doesn’t work if you don’t control the entire server.
I decided to look for a “better” solution. One where my speedy toys would still work. I came up with the options below.
Option #2a — Disable mod_pagespeed for /wp-admin/ via module
If you run multiple WordPress sites, or otherwise have control over the entire server, I suggest you make the changes at module level. Edit
/etc/apache2/mods-available/pagespeed.conf and at the bottom (Before ) of the file add the following:
<Location /wp-admin/><br /> ModPagespeed Off<br /> </Location>
Now restart Apache and you should be good to go. Any /wp-admin/ on any site will have the module disabled. This is the “safe” way in my book; you only need to worry about something breaking if mod_pagespeed is updated.
Option #2b — Disable mod_pagespeed for /wp-admin/ via .htaccess
If you only run one copy of WordPress, or do not have access to the entire server, you can selectively disable this module in the .htaccess file. Edit said file for your WordPress site and add the line:
That’s it! Next time you reload the admin pages, mod_pagespeed should be turned off and the buttons work again. You may need to force refresh your browser, but otherwise this change should be instantaneous. If it doesn’t work, your hosting provider has locked you down and you need to talk with them.