• I was advised by Dreamhost Support to set up WP Super Cache using mod_rewrite as outlined in their support article here:

    https://help.dreamhost.com/hc/en-us/articles/214588698-Installing-WP-Super-Cache

    My .htaccess file continues to reflect this option, though mod_rewite doesn’t seem to be an option anymore since the last plugin update.

    The site –?and indeed the server that hosts it –?have been acting up since the update, even crashing the server multiple times, requiring a power cycle to bring it back up. I can’t help but wonder if my Super Cache settings are contributing to the problem.

    In addition, there no longer seem sot be a “Preload Cache Now” button under the preload tab.

    Is this all by design, or is something gone wrong with my plugin installation?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Mod_rewrite is now called “expert mode”, so select that if you need it.

    Do you have caching enabled before looking at the preload page? I see a “Preload Cache Now” button at the bottom of that page.

    Thread Starter halfacre

    (@halfacre)

    Thanks for the reply, Donncha.

    Good to know, I’ve set it to Expert Mode. Made sure to update both .htaccess files just to be on the safe side. I’m guessing it didn’t help that at first I didn’t put these caching rules at the top, as the page tab states. Rectified that error as well.

    Regarding the Preload tab, yes, caching is on:
    https://snag.gy/UmfODp.jpg

    But the Preload tab looks like this:
    https://snag.gy/lFyKth.jpg

    I keep looking again to see if I missed it somehow… it wouldn’t shock me at this point.

    Thanks again!

    Preloading is already active. In the screenshot you showed, the next preload was going to happen in just under 9 hours. You can cancel it by clicking the “Cancel Cache Preload” button.

    I have the same problem with version 1.5.2 installed. When I select the cancel preload button it does nothing, the button Preload Cache Now is not displayed.

    Wait for it to automatically preload in 30 min and not run. I return to version 1.4.9 again in less than 3 days ??

    • This reply was modified 7 years, 7 months ago by Diogenes. Reason: Wait for it to automatically preload in 30 min and not run
    • This reply was modified 7 years, 7 months ago by Diogenes.
    • This reply was modified 7 years, 7 months ago by Diogenes.
    Thread Starter halfacre

    (@halfacre)

    I don’t want to cancel the preload, but I also was hoping not to wait 9 hours for the cache to preload, thus why the “preload now” button is useful.

    So the button not showing up is expected behavior?

    You don’t need to wait 9 hours for the preload to go, just cancel it and the cancel button changes to a button that says “Preload Cache Now”.

    Thread Starter halfacre

    (@halfacre)

    Ah, I see… Got it. Thanks Donncha. Is this a new feature for 1.5.2? I can’t recall for sure, but I thought in the prior version, when I had scheduled preload the button showed regardless. I could be wrong.

    Sometimes I need to clear the cache and then preload it again on the spot, but still would like to keep the scheduled preload running. It’s a small thing to tick the box again (if even that’s necessary), so no big deal either way.

    Thanks again!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘“preload cache now” and mod_rewrite options not available after 1.5.1 update’ is closed to new replies.