slapbox

Hey @j_3rk thanks for your reply. We’re not using multi-role, and only admins can access the dashboard so I’m afraid I can’t answer whether it only affects administrators without quite a bit of work. We’re not using multi-site.

I didn’t see any tutorial per se. I did click through every screen and look for any option that might be relevant, but couldn’t find anything to fix this.

—-

Right before I hit submit on this message, I found a solution.

Go to the “Role Based Timeout” tab. Hit “Save Changes” on this screen, rather than pressing “Save Changes” the “Basic Management” screen and the problem ceases. Thanks for your great work!

@j_3rk any thoughts?

Hey @wfdave thank you for your reply!

Unfortunately remote scan didn’t work, but that did help me find the debugging option which allows me to see the cause of failure, which is, Scan process ended after forking.

I read the relevant part of the scan troubleshooting docs, but I’m unclear on this bit: “Memcache may have to be restarted twice in order for the object-cache to get rid of the saved cron key.”

We are using memcache via W3 Total Cache, but purging the cache, disabling it, disabling W3TC, and rebooting the server all fail to remedy the issue.

How would one restart memcache twice in this scenario, and is that relevant in an environment which includes define('DISABLE_WP_CRON', true);

Hey Gabe thanks for your reply! That does indeed fix it.

Hey Marko, I actually made that change on my own in the nginx.conf – but the rules I shared are the output of W3TC’s rules. I tried a bunch of things to get it working within WordPress/W3TC before making the issue. If anyone else has this issue, it might point to some issue with W3TC updating the nginx.conf.

Thanks for your help!

Hey Marko, thanks for your reply.

We’re not using Apache at all, only Nginx. Here’s a pastebin of the nginx.conf output for W3TC. woff and woff2 don’t seem to be mentioned. https://pastebin.com/Btx7dmLS

No other directives we have affect woff/woff2 files either.

• This reply was modified 4 years, 9 months ago by slapbox.

Hey @j_3rk sorry for the horrible ambiguity. Here’s what I mean: https://imgur.com/a/q9aVtz5

I’m not sure why, but it appears every time I change screens in the admin area. Any ideas?

It also doesn’t seem to automatically log me out as an admin with the timeout set to 1 minute. No warning and no logout. I can share more information, but I’m not sure what would be helpful diagnostically.

Thanks for sharing your work and for your assistance with this!

Also, the favicon png and webmanifest

Oddly, seems to affect more fonts on Firefox?

GTMetrix Firefox

GTMetrix Chrome

• This reply was modified 4 years, 9 months ago by slapbox.

Your instructions fixed Autoptimize minification. W3TC minification 100% does not work. I’m not using it, so fine – but I wanted to let you know. It still identifies 0 files of any type for minification.

@vmarko thanks for your reply. Is there somewhere I can download 0.12.x?

Reverting to 0.12.x seems most likely to work, given that I’ve done everything except remove the wp-content/plugins/w3-total-cache and the w3t-config folder, which I will try – but have low hopes for and need something working ASAP in the interim.

We also did the equivalent of cleaning out the .htaccess file (cleaning out the nginx.conf file)

Also, if reverting to 0.12.x does resolve the issue, would that be of diagnostic value to you?

Thanks again!

Hey @vmarko and @optimizingmatters – thanks for your response. Sorry I wasn’t clear.

We were using Autoptimize to minify, but stopped after upgrading to 0.13.x because suddenly minify files were no longer generated. At that point we opted to turn on minify in W3TC, but we ran into the same issue.

So to be clear, using only W3TC, the minification issue persists. We have deleted the wp-content/cache folder and ensured proper permissions, but no dice. I should note that our server does not allow access via loopback, which I know can cause issues with many plugins. It didn’t cause any issues previously. We were on 0.12.0 prior to this, without any apparent trouble.

If I turn off W3TC, Autoptimize immediately resumes minification of files, which makes me feel confident that W3TC is somehow the cause of breaking both its own minification, and 3rd party minification.

I love both plugins and would love to keep using both, but I’d settle for getting W3TC minification working. I also tried a few other minification plugins since. None of them worked with W3TC either, although I don’t have a baseline to prove that those ones ever would have worked.

Diagnostically speaking, W3TC’s minification helper screen for manual mode shows nothing to minify, either JS or CSS, which I suspect might point the development team to the issue if anything I’ve found does.

• This reply was modified 4 years, 9 months ago by slapbox.

Hey @wfdave – does this mean there’s no way to use the scan functionality on a site using HSTS? We’re using a Cloudflare origin cert for our SSL and we get:

wp_remote_post() test back to this server failed! Response was: cURL error 60: SSL certificate problem: unable to get local issuer certificate

Is there no way to use the scan functionality besides mangling our SSL cert config (swapping it out for one from Certbot), cloning the site to a completely new environment (a day of work), or disabling HSTS (not an option)?

Thanks for reading! Any advice would be great!

@tundeaj I hope once this is fixed you’ll revise your review. I am so blown away by this plugin that it makes me personally sad to see it with even one 2 star review for something so easily fixed.

Turned out to be an issue with running WP_CRON. Timing seems coincidental. Thanks again!

XIBO, My backups ran fine until one day I ran out of disk space. I’ve since resolved that, my MySQL database is perfectly in order, I have WP_DEBUG enabled, and I’ve checked my browser’s console, the wp-content/debug.log, and my PHP log, but there’s no errors to be found anywhere.

I restarted the plugin, but that made no difference. Backups say they’re starting, then after a moment the page refreshes and that’s the end of that.

Do you have any ideas? Thanks for your great plugin!