Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter jardeath

    (@jardeath)

    Interesting, I don’t have a .htaccess as I’m using Nginx, I’ve basically transferred the configuration into my Nginx configuration though.

    This is still a problem I have, over the weekend I get around 10 instances of preloading as previously outlined before it will eventually be fine for a few days, but still not the full week specified.

    Thread Starter jardeath

    (@jardeath)

    I suppose that may be an option, at 0 it wouldn’t auto preload and would just keep the preloaded cache.

    I assume that having the setting enabled to do the preload if you edit a post or post something new would be enough to trigger it when required.

    Edit: Nope it did not start a preload, it did delete the cache files though as the setting stated but it doesn’t start generating them again, so 0 might not be an option for me.

    Is setting to preload every 7 days perhaps too long or something and what causes this problem?

    Thread Starter jardeath

    (@jardeath)

    Still happening, any ideas?

    For 4 or 5 days it was fine, now in the last hour it’s done a full preload about 4 times. One just finished and it says:

    Full refresh of cache in 0 hours 30 minutes and 12 seconds.

    Despite it being set to 10080 minutes it seems to start much sooner, I still get emails saying preload has completed and the next will be in 10080 however when I check the preload tab the time to next preload is much sooner. I am not making any changes at all to anything to cause a recache.

    After the above ~30 mins preload started again, and the countdown changed to “Full refresh of cache in 0 hours 3 minutes and 33 seconds.” then after that time was up preload kicked off again and showed “Full refresh of cache in 0 hours 3 minutes and 50 seconds.”.

    Now after that it’s “Full refresh of cache in 22 hours 52 minutes and 11 seconds.”, better than every 3-30 mins but still not the specified 10080 mins.

    jardeath

    (@jardeath)

    Yeah seems to have started working for me as well since 4.2.2

    Thread Starter jardeath

    (@jardeath)

    So I’ve fixed the problem, I think the problem was that the preload was trying to hit the full URL of the site when doing the GET requests, problem is DNS points to my old server. I added my domain to /etc/hosts for 127.0.0.1 and instantly the preload begun.

    This explains why when I changed the site URL it worked, because that particular URL I changed it to correctly resolved to the server.

    It’s a bit strange that the .gz white page bug seems to have disappeared to without the plugin being updated, I saw in another post it was patched in the dev build only so far.

    Thread Starter jardeath

    (@jardeath)

    I think I’ve narrowed it down a bit more, I recopied the whole site over from the old working server to the new one and the same problems were back.

    I turned on debug mode, turned on gzip, disabled debug, turned on gzip, and the files are now generating correctly.. Preload still not working however.

    I then went to test something else and I changed the name of the whole URL in General for the wordpress site itself, I then found that under the new name it had preloaded all of the pages into a new supercache directory with this new name somehow, but not the original correct name.

    Is there any other way to make a preload happen? I’m thinking of just making something to run a GET on all posts every week or something.. Can anyone provide further info on what happens when you actually click preload? What should I look into? What is it that makes the pages request? I don’t see any requests coming into the logs at all as you normally would when it works.

    Thread Starter jardeath

    (@jardeath)

    I turned on the debug option in the plugin, and the cache files started generating again. Turned it back off and still working. I have no idea how that resolved the problem, or if it will crop up again.

    This also seems to have fixed the .gz files generating without the initial white page, the bug resolved in https://wordpress.org/support/topic/421-initial-blank-page-load?replies=15 however I don’t think this has yet been patched outside of the dev version, so no idea what’s going on there.

    It did not fix preload however, which still does not work.

    Thread Starter jardeath

    (@jardeath)

    Now when I load the page for the first time, the supercache directory for the page is created, but the .html and .gz pages are no longer created. I think the .html files are being created in the legacy area however, though not sure why.

    I do have the message still about there being no mod_rewrite (correct, Nginx is in use), does the code disallow this mode working properly if mod_rewrite cannot be detected?

    jardeath

    (@jardeath)

    Interesting, I seem to be having the same pre load issue as I detailed here: https://wordpress.org/support/topic/preloading-not-working?replies=1

    CentOS 7
    Nginx 1.8.0
    PHP 5.6.8

    What are you using? Perhaps this information may help us get to the bottom of it.

    jardeath

    (@jardeath)

    Noticed I was having this problem after turning on gzip for the first time today, glad it’s only a recent issue and not just me.

    Any idea how long before we will see an official update to the plugin to patch this problem, rather than having to use the development version?

Viewing 10 replies - 1 through 10 (of 10 total)