IDX Broker not compatible with caching plugins

  • dragozir

    (@dragozir)


    7 years ago

    Using Autoptimize, cache enabler(for webp), and WP Asset CleanUp definitely has some edge cases which are causing my IDX pages to break (i.e. stylesheets have their names changed and can’t be found). Now I know that the wrapper updates every half-hour, but after clearing the wrapper cache, the website was still without CSS until I disabled Autoptimize. Additionally, I was able to verify prior to clearing the wrapper cache and disabling the plugin that my pages that use the post layout that I used for my wrapper were working (in an incognito tab with no previous traffic to my domain/idx pages). I had been using WP Asset CleanUP to remove styles and js the easy way in an attempt to make these future proof but I may end up having to get my hands a bit dirtier. I have used W3 Total Cache before and am going to try switching back and posting my results. I really value caching plugins for their ability to reduce load times but their often cryptic, unchangeable naming conventions are a headache in their own right. Does anyone have any tips or tales of their own successes/failures on this subject? I’ve heard mentions of version numbers but I’m struggling to find resources/excerpts/documentation from IDXBP users trying to make cache plugins work.

Viewing 1 replies (of 1 total)
  • Thread Starter dragozir

    (@dragozir)

    Forgot to mention: this is the second instance of this happening, where changing assets in WP Asset CleanUp has caused my Autoptimize css cache to update (good!) and my idx pages to break (bad!). I’m thinking about adding some custom js to my page template as a fallback like the following pseudocode

    if (document.getElementByID('mySheet').cssRules != null)
    var sheet = document.createElement("link");
    sheet.rel ="stylesheet";
    sheet.href ="/my/absolute/path.css"
    link.id="mySheet"
    document.GetElementsByTagName("head")[0].appendChild(sheet);
    // recurse with a console.log to verify

    which is dumb bloated boilerplate I want to avoid, and the fact that it’s going to make my idx pages have higher loads times, although less downtime, is something I’m heavily considering it since it would at least keep the site usable for those edge cases.

Viewing 1 replies (of 1 total)
  • The topic ‘IDX Broker not compatible with caching plugins’ is closed to new replies.