• Nikelaos

    (@nikelaos)


    Hello!

    First of all: Thank you for your plugin!

    I have a little “problem” (the site works, BUT…):

    I have the “404 to 301”-plugin installed, which alerts me by mail about 404-errors. I’ve installed your plugin yesterday, and as I were checking my e-Mails just now, there were a mass of 404-alerts (near 1000) that reached me.

    So I checked this.
    I called a page of my site and get 13 404-messages. The file, that were raising a 404 look like that:
    at first “/my-category/my-page/my-subpage/60989FDAC33AB7A64C54F0519FD41ABA.cache.html/”, followed twelve times by “/60989FDAC33AB7A64C54F0519FD41ABA.cache.html/”
    In my browser (actual firefox-version) I saw, that the page were loaded in a short time (for my sentience…), but the loading-indicator (the animated blue circle on the tab) was activated over about 5 seconds or something more, a very long time (for my sentience…). I deactivated the autoptimize-plugin, called the same page again – delivered not much slowly as before (for my sentience…), the blue circle vanished quickly and I got no 404-mails.

    I use “WP Super Cache” also, WP is a single-site/subdirectory-installation, so my website-URL is “https://xxx.dom”, my WP-URL “https://xxx.dom/wordpress”

    How can I fix this? Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Frank Goossens

    (@futtta)

    that does not look like something Autoptimize would do @nikelaos, AO only caches autoptimized JS/ CSS-files which typically have /wp-content/cache/autoptimize/js/autoptimize_xyz123.js or /wp-content/cache/autoptimize/css/autoptimize_abc456.css as filename.

    60989FDAC33AB7A64C54F0519FD41ABA.cache.html looks like something a page caching plugin would use, but I’m not sure this is wp super cache ..

    frank

    Thread Starter Nikelaos

    (@nikelaos)

    Well, I saw the folder in wp-content/cache.

    But: If I deactivate your plugin, the behaviour vanishes… so I thought the reason is located in your plugin. Where else should I look, what else should I check? Is it possible that “WP Super Cache” is the source, in combination with “Autoptimize”? Should I contact the authors of “WP Super Cache”?

    Nikelaos
    P.S.: I took a look into /ccs rsp. /js subfolder and find same “autoptimize_…” files there…

    Plugin Author Frank Goossens

    (@futtta)

    WPSC + AO is one of my own preferred combo’s, never seen this happen before.

    the only thing I can think of is if you have some a plugin that is adding JS that requests cached content and that plugin’s JS breaks when being autoptimized, causing the errors?

    Thread Starter Nikelaos

    (@nikelaos)

    Well, looks like that. I’ve tested the pref. combo on a WP-test-inst. and it worked well.
    So I think, I have to deactivate plugin by plugin to check out which plugin causes the behavior?

    Urgh… there’s a lot of plugins… any ideas, hints or suggestions? Wordfence I’ve checked… I’m using “CSS & Java toolbox”, could this be the problem source? I’ve checked all .php-files with bluefish for “cache.html” but only “browsercache.html” of deactivated “W3 Total Cache” was found… I’ve checked “.html” the same way and didn’t find anything suspicious… I’ve deleted the inactivated plugins “W3 Total Cache” and “WP Fastest Cache” (that’s a bit silly, yes, but…) – no of these steps helps.

    Well… ??

    Plugin Author Frank Goossens

    (@futtta)

    no idea what “css & java toolbox” does i’m afraid. w3tc & wpfc as such I know, never seen such behavior there either ..

    Thread Starter Nikelaos

    (@nikelaos)

    With “CSS & Java Toolbox” you can write CSS & Java-Code for selected pages – I think, it will be inserted at the moment of delivery.

    Never seen – well, have anybody who uses the plugin does “404 to 301” installed with the option for logging 404-request activated? What I mean: Perhaps no one has noticed so far…

    I have cross-checked the combination: If “WP Super Cache” is deactivated, the behavior does not change…

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘404 for xxxx.cache.html’ is closed to new replies.