Support » Plugin: W3 Total Cache » [Plugin: W3 Total Cache] Disk-enhanced page caching impossible w/o permalink trailing slash?

  • 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

    http://wordpress.org/extend/plugins/w3-total-cache/

Viewing 15 replies - 1 through 15 (of 26 total)
  • May I second that, I’d even be willing to pay for this feature.

    Please let us know if we can remove the RewriteCond or if we’ll run into any problems

    For SEO reasons its impossible to add a trailing slash and I’m sure that there are many others out there who don’t want to update their permalink structure and mess around with some 301 redirects. Goolge will index both in the end if you don’t take care..

    Anyway, W3T is pretty cool, nice work!
    Oliver

    Same things here, my permalink structure ends with .html so I cannot add a trailing slash and everything has always worked fine.

    Same here…Got this message after upgrading to 0.9.2.1 and now cannot re-activate the plugin. Hopefully the developers are reading this :/

    Ouch…none of my pages cache now. My pages end in *.html.

    Caching: disabled
    Reject reason: request URI doesn’t have a trailing slash

    This was a strange change to make as I noticed that even for category pages like domain.com/my-category/ (WITH the trailing slash) these forward to a non-trailing slash version and are then not cached as well!

    Guess we need to roll back to an older version until this is addressed .. ?

    Same here, I’m getting this error…

    “The permalink structure (/%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.”

    I don’t want to alter /%postname% if it’s going to affect my SEO and cause me to lose traffic. My other site ends in *.html. I’ve never seen anyone use a permalink *.html/

    So it appears one option is install another cache plugin like WP Super Cache which I don’t like or keep W3TC and add the ending slash then do 100s of redirects for all of my sites.

    keep W3TC and add the ending slash then do 100s of redirects for all of my sites.

    SEO, you already chose .html. Software should meet your config. Dont to that.

    Submitted a bug report. Hopefully Frederick sees this thread soon :/

    Hello Frederick, can you please let us know;

    Why does the new W3TC plugin version forces sites and blogs adding trailing slash at the end of url’s?

    Many people use .html or .php etc. at the end for years. Many sites/blogs also use %postname% instances with no the ending trailing slash.

    * Is there a related fix by support if we pay you a support fee you require?? Or how to set this up.

    With compliments and anticipation! Thank you.

    where is everyone seeing that error?

    I haven’t seen it myself but I wonder if i’m not looking in the right place.

    It’s not an error, it appears to be by design. I’m really surprised they did not think this would effect a lot of people. We upgraded to the latest version of W3TC and caching has stopped working due to our URLs not ending in a trailing slash. Very strange as last I checked .html was a pretty common extension for HTML pages.

    If you want to see if this effects you turn on page caching and the debug code for it. Then view-source on one of your posts/pages. Look for the message below.

    Caching: disabled
    Reject reason: request URI doesn’t have a trailing slash

    The basic disk mode seems to be buggy as well.

    I’ve been using it for a couple days and today I noticed that when W3T Page cache (basic disk) is enabled, it sometimes turns the permalinks into the regular links (p=2039), disabling the permalinks completely.

    How would I create a debug report?

    Has anyone successfully reverted to an earlier version? Doesn’t look like a fix is coming soon. Must be a lot wrong with this new version.

    Use WP Super Cache. It now includes CDN support also have a look at how active the developer is with the community.

    Good luck!

    i’ll try it… i thought w3 cache was rated as the best in the business?

    Its great dont get me wrong there’s just too many bugs. But for me its a lot about support. The WP Super Cache developer is a genius who is friendly, humble and “very active” in the forums:

    http://wordpress.org/tags/wp-super-cache?forum_id=10

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