Apparently not working?

  • Resolved Diplo

    (@diplo)


    12 years, 8 months ago

    Hi Emre,

    I’m making tests with the plugin. I’m using a WP installation with Twentythirteen theme, 2 posts and WP Fastest Cache activated. What I’m doing is:

    1. Load a post with <?php echo date(“D M d, Y G:i:s”); ?> as <title> in header.php;
    2. Check the time;
    3. Open a new browser tab;
    4. Check the time and compare it with the previous one: title of the page and creation time and date are different.
    5. Open a new browser, access the same post page, compare the creation time: they are all different.
    6. Open another browser and repeat the test. Same results.

    Apparently, the cache pages are being created but not delivered. If the cache was working, all the pages should have the same time as page title. What could be wrong?

    Cheers!

    http://ww.wp.xz.cn/plugins/wp-fastest-cache/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Emre Vona

    (@emrevona)

    12 years, 8 months ago

    Hi diplo, first of all thanks for test…
    but I couldn’t understand the issue. Can you show me an example?

    <!– WP Fastest Cache file was created in 0.0896680355072 seconds, on 18-10-13 18:41:14 –>

    If you see such tag under the page, that page has already been cached.

    Thread Starter Diplo

    (@diplo)

    12 years, 7 months ago

    Sure Emre, have a look: http://www70.zippyshare.com/v/58228841/file.html

    In the first load, the page is created and cached on Sat Oct 19, 2013 8:38:34 (I added current time as blog description); below the image you can see the WP Fastest Cache source tag.

    In the second load, what is expected is to see the page cached in the first load, but what is being displayed is a new page generated at 8:45:35. I’ve tried this with other browsers and the result is the same.

    In wp-content/cache/all I can see the generated html file (3rd screen capture), which corresponds to the first load (no idea where is the 2nd page being stored then).

    Apparently the plugin is missing the final step: to load the page in cache.

    Thread Starter Diplo

    (@diplo)

    12 years, 7 months ago

    Hi Emre,

    I found the problem. I kept testing on different servers and the issue was that in some the .htaccess file contained weird paths to the cache folder (like RewriteRule ^(.*) “/wp-content/cache/all/nfsc06h04mnt175162domainsexperimentnlhtml/$1/index.html” [L]).

    After setting the path right again, the plugin works perfectly. I made the same tests as before and all delivered the page in cache. Great solution, thanks a lot for this plugin!

    Plugin Author Emre Vona

    (@emrevona)

    12 years, 7 months ago

    your welcome 🙂

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

The topic ‘Apparently not working?’ is closed to new replies.