• Hi Frederick,

    I upgraded to 0.9.2.1 and saw this message:

    The permalink structure (/blog/%postname%) does not include a trailing slash, disk enhanced page caching will fail to cache most requests. Either switch to any other supported caching method or add a trailing slash in the settings.

    My permalink structure does indeed lack a trailing slash, and with earlier versions of the plugin I had removed this rule in .htaccess —

    RewriteCond %{REQUEST_URI} \/$

    — and disk-enhanced page-cache files (wp-content/w3tc/pgcache/*) seemed to be served with no problem. Can I continue to do this and still use disk-enhanced page caching successfully?

    Thanks, Sam

    https://www.ads-software.com/extend/plugins/w3-total-cache/

Viewing 11 replies - 16 through 26 (of 26 total)
  • Did anyone install the new update yet – 0.9.2.2 version?

    Does it still ask for a trailing slash for the permalink?

    Not really sure if it totally works but the changelog says its fixed. I haven’t installed it yet however but will soon.

    https://www.ads-software.com/extend/plugins/w3-total-cache/changelog/

    So I installed the latest(?) development version (marked 0.9.2.2b) and I get this in my debug code:

    Engine: disk (enhanced)
    Cache key: _index.html
    Caching: disabled
    Reject reason: Requested URI has a trailing slash
    Status: not cached

    Ironic, huh. This is on my home (loop) page. When I go to my about page, which has no trailing slash, here’s what I get:

    Engine: disk (enhanced)
    Cache key: about/_index.html.gzip
    Caching: enabled
    Status: not cached

    Not cached, no reason given. I’m logged out at the time, and refreshed a couple of times. Don’t see any files in pgcache. Seems like, one way or another, no caching for me.

    Version 0.9.2.2 mentions:
    Fixed bug with fancy permalinks, sites with or without trailing slashes can now cache pages using disk enhanced.

    If this is the same bug it seems like it’s still happening.

    Thread Starter sam_a

    (@sam_a)

    @max_q: I also see “Reject reason: Requested URI has a trailing slash” in the page cache debug message for my home page using 0.9.2.2 (my permalinks lack trailing slashes).

    I think this is a new bug that came with a new feature — instead of rejecting all URLs with a trailing slash, 0.9.2.2 caches only URLs that match your permalink structure (i.e. with or without a trailing slash). It should skip that check for the home page URL (/), which always has a trailing slash.

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    This issue is fixed in the latest release.

    I am running 0.9.2.3 and when I view debug info for my home page, it says it is not caching it due to the slash…

    Please help.

    <!– W3 Total Cache: Page cache debug info:
    Engine: disk (enhanced)
    Cache key: _index.html
    Caching: disabled
    Reject reason: Requested URI has a trailing slash
    Status: not cached
    Creation Time: 1.739s
    Header info:
    X-Pingback: https://www.—&#8212;.com/—–/xmlrpc.php
    Content-Type: text/html; charset=UTF-8
    X-Powered-By: W3 Total Cache/0.9.2.3

    When Frederick said:

    >>This issue is fixed in the latest release.

    Did he mean in 0.9.2.4?

    I think he did, as the code that generates the reject reasons in .4 is vastly different than .3.

    Rich

    Also in 0.9.2.4 there is this issue, but not only for homepage or pages with or without trailing slash, it is for all pages!!! See here:
    https://www.ads-software.com/support/topic/bug-disk-enhanced-cache-doesnt-work-in-0924

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    W3TC now has an option that allows you to cache all requests or only those consistent with your site URL. Please have a look at that option and let me know if you’re still having the issue via a bug submission form from the support tab of the plugin.

    I also recommend checking out the development release.

    Thanks Frederick, I’m already using the latest development release (0.9.2.5b) and I have the issue on 5 different blogs.

    I have tryed Disc Enhanced with and without “Cache requests only for 12n3.com hostname” but the result is the same: status not cached.

    I have already submitted the bug via support tab. I’ll do it again.

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    Thanks

Viewing 11 replies - 16 through 26 (of 26 total)
  • The topic ‘[Plugin: W3 Total Cache] Disk-enhanced page caching impossible w/o permalink trailing slash?’ is closed to new replies.