• After running the Cache Tester, it produced the following results.

    Fetching https://mywebsite.com/ to prime cache: OK (0.html)
    Fetching first copy of https://mywebsite.com/: OK (1.html)
    Fetching second copy of https://mywebsite.com/: OK (2.html)

    Page 1: 200 (OK)
    Page 2: 200 (OK)
    The pages do not match! Timestamps differ or were not found!

    Could it be WP Super Cache cannot work on any shared server if the Local and Maser values for date.timezone are different? If so, is there any way to get around this timezone issue so that WPSC can work?

    Please advise. Thank you.

Viewing 5 replies - 1 through 5 (of 5 total)
  • I don’t know, but just test it manually as suggested on that page. View source, compare time stamps, etc.
    Or use the debug log to make sure that a cached file was used to serve the page.

    Thread Starter Jason Wong

    (@eljkmw)

    @donncha Did you check your system’s PHP info on whether the local and master values of date.timezone are identical, or difference? I’m guessing if they’re different, the timestamps will definitely be different and the pages won’t cache.

    Thread Starter Jason Wong

    (@eljkmw)

    Just ran a test with both local and master values being the same at UTC, and the results are still the same. This is very odd indeed.

    My server time is set to UTC and WordPress time changes between UTC and UTC+1 with no problem. How do you set a master and local timezone? Different virtual hosts have different timezones?

    Thread Starter Jason Wong

    (@eljkmw)

    @donncha
    The master timezone is set to UTC by the hosting provider, while I can set the local timezone either via .htaccess or php.ini. I’m not using any virtual host, but a shared host.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Can WPSC run on shared server with different date.timezone?’ is closed to new replies.