Steve

What exact issue did you run into?

@joeldauteuil — when you ran into this, did a full uninstall of W3 and re-install resolve the issue?

@z4reg — not sure why you posted this information in this thread. Does not seem to be related to the specific issue I had listed in this thread.

Did more research and found root cause — at least the reason this is happening….

For whatever reason, if you try to open a page without a trailing slash / the blank page will be cached and then displayed to the visitor.

I can repro this over and over….

I still need to see if I can repro this on other sites as it might be a conflict between W3 Total Cache and another plugin I’m using…???

For now, I’m using an .htaccess command to just add a trailing slash to everything.

# Add trailing slash
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)([^/])$ /$1$2/ [L,R=301]

Would be curious if you have any thoughts on this.

-S

More information.

Looking through the file structure with my FTP client. The pages which show up blank look exactly the same at a file level however when you download the cached page via FTP — it’s empty.

I delete the blank cache file then refresh the browser window and the page will always refresh without issue for me.

So again, I have blank pages being created but I don’t see a repro step yet on this.

-S

@joost — I can confirm that yes, I’m using a static front-page on Canvas and I can also confirm the DEV version of the code fixed the problem.

The only other thing I noticed is the front-page does not include and rel=”next” /page/2/ like it does on the home page of a blog not using a static page for home page. Not a huge deal as I’m sure google will figure it out and, all the other pages don’t have a problem with this.

Thanks,

-S

@joost — Correct. Let me test it out and get back to you in a few hours.

Just heard back from WooThemes DEV on this issue. They are pointing things back to the plugin creator unfortunatly…

Thanks for your query and welcome to the WooThemes Support Forum. ??
To clarify here, you are correct regarding the pagination URL structures being different for archives vs pages. That being said, the “/page/” rewrite rule does work on single pages, and is commonly used for page templates that generate paginated archives such as the “Magazine” template bundled in Canvas.
In terms of the “next” and “prev” URLs, this may be a bit trickier, as these URLs are generally used on archive screens, where a clear “previous” and “next” post is available.
In terms of resolving this, I believe the best port of call here would be to contact Yoast directly, as these URLs are generated/manipulated by the WordPress SEO plugin, I believe. The canonical and “next”/”prev” URLs in question here would be the way they are currently for any page template used as your front page (or as a sub-page, for that matter) and isn’t specific to Canvas.
If Yoast requires that lines of code be added to the theme in order to support functionality added to his plugin for this functionality to be present, please let us know and we’ll see about adding the code to Canvas. ??
Thanks and regards,

So until the plugin is updated to support a magazine type theme like Woothemes Canvas, I’m stuck.

@yoast?

Thanks!

@aahan – great updates. Thnx.

FYI – Reverted to a different plugin for now until I can get this working. FYI in case you check the links above.