[Plugin: WP Super Cache] Permlink Structure Error

So are you using ?p=xxx for your urls? Those links will still work even when you have custom permalinks!

Ok, thanks. Any recommendation of permalinks I can use? I envisage /%postname%/. Is it ok?

Yeah, that’s fine.

Thanks a lot!

But how about PR?
Will pages loose it after moving to pretty permalinks?
Or WP SuperCache & WordPress (3.0.1) do 301 redirections automatically for all posts and pages?

Information in the web is contradictory on the subject. Could you help please?

Thank you for all the hard work on Super Cache. I’ve been using it for two years.

So, nobody know the answer?
Could someone give me a link to clear explanation if this question really stupid and doesn’t deserve to be answered here.

It’s pretty easy to test, look at the headers sent by the server when you request a ?p=xxxx request and it redirects. WordPress sends a 301 redirect so the PR is transferred.

Thank you very much for your reply and all the efforts creating WP Super Cache.

I would advise against just using /%postname%/ as your URL structure.

You can read a bit about it here:

https://codex.www.ads-software.com/Using_Permalinks

“For performance reasons, it is not a good idea to start your permalink structure with the category, tag, author, or postname fields. The reason is that these are text fields, and using them at the beginning of your permalink structure it takes more time for WordPress to distinguish your Post URLs from Page URLs (which always use the text “page slug” as the URL), and to compensate, WordPress stores a lot of extra information in its database (so much that sites with lots of Pages have experienced difficulties).”

For a balance of performance and SEO I typically recommend:

/%year%/%month%/%post_name%/

or https://mydomain.com/2010/11/post_name

skippybosco – going against all the recommendations I use /postname/ as the permalink structure on my blog and it works well. Once all posts are preloaded they’re served by mod_rewrite rules anyway so there’s little processing to be done ??

I’ve installed following permalinks structure:
/%year%/%monthnum%/%day%/%postname%/

It works for posts, e.g.:
https://www.holoborodko.com/pavel/2009/07/17/rikugien-garden/

But URLs for pages became /%postname%/ anyway:
https://www.holoborodko.com/pavel/quicklatex/

I’ve checked HTTP Headers by Fiddler – /?p=xxxx are being correctly redirected – so I’m happy.

It seems like WP makes permalinks for pages of /%postname%/ style regardless of user settings.
Or am I missing something?

Just noticed,

Sometimes Fiddler give error message on loading page (in IE) cached by Super Cache (in preload mode):
“The Server did not return properly formatted HTTP Headers. HTTP headers
should be terminated with CRLFCRLF. These were terminated with LFLF.”

Is it a big deal? Page are being loaded properly in the browser anyway.
When I load page in FireFox – no complains from Fiddler appear.

advanpix – pages are always served that way. I’m not sure about the headers as Supercache uses Apache modules to serve them and I would have thought they’d work properly but I’ll keep it in mind.

Thanks for clarifying!

Hi there,

I am trying to resolve the same issue as above. My default setting is https://www.websitename.com/?p=123. I need to understand this in layman’s terms, so would I highlight custom struture and change my permalink address to https://www.websitename.com/%postname%/ to get this error fixed? If you could explain it with the example I’ve used, and in layman’s terms, it would be greatly appreciated.