Hi Ben;
A page often matches multiple conditional tags, so it might be that the one you’re waiting for is never gotten to because another tag matched? if you want to find out, enable “debug mode” and then in a anonymous browser window request the page(s) that match the tag you’re targetting and then check in wp-content/uploads/ao_ccss/queuelog.html what tag matched those requests?
frank
Hi Frank,
We have this exact same issue with a staging backup/restore of our production website. We’ve been navigating thru the site with anonymous sessions and we can’t get anything other than the is_front_page AUTO rule.
We also tried enabling the debug mode, but we only get a message about the API Key validation and some queue locking logs… but no new auto rules created. Our production site does in fact have multiple AUTO rules for all of those pages, so wonder what’s keeping the _staging_ restored instance from creating them.
2020-09-28T23:15:07+00:00 - [DD] criticalcss.com: API key is valid, updating key status
2020-09-28T23:17:23+00:00 - [DD] criticalcss.com: API key is valid, updating key status
2020-09-28T23:23:51+00:00 - [DD] Queue control started
2020-09-28T23:23:51+00:00 - [DD] Queue control locked
2020-09-28T23:23:51+00:00 - [DD] Queue control unlocked
2020-09-28T23:23:51+00:00 - [DD] Queue control finished
Not *really* the exact same issue, as Ben wrote
I see many conditional tag-based rules that are “AUTO”
Mauricio so next time do make a new topic maybe 🙂
Now re. you problem; might staging have very aggressive page caching, resulting in requests not reaching WordPress/ Autopitimize?
Thanks @optimizingmatters, well I didn’t state it but our production version (the one we took the backup from, it does have a lot of AUTO rules (just like @bcupham stated 🙂 ).
Not really, our staging (and production) only cache assets in a separate CDN url (which we also configure using Autoptimize)… these requests should be getting to WP for sure… BUT, and we noticed this this morning, the Autoptimize cache is mostly empty (2 files, 0.0KB). I wonder if for some reason Autoptimize simply isn’t being triggered by the WP request handling somehow…
We’ve tried deactivating/reactivating AO and also tried removing and readding the CCSS API key… no luck.
We thought it must be that with the restoring of a production backup into a different site name and port (staging.<originalsite>.com:30000) maybe whatever state it had just wasn’t compatible… but reinstalling the plugin didn’t seem to fix that so here I am asking for help.
OK, but can you indeed create a new topic for this to avoid confusion (and because the forum guidelines asks to do so)? 🙂
thank you,
frank