Permalinks not working

Using_Permalinks

Thanks for the link Moshu – I’m a bit of a WordPress novice though; which section should I be looking at?

3. Using Pretty Permalinks

Thanks. I still can’t work out the problem though. I have checked my .htaccess file, which reads:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /blinds-blog/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blinds-blog/index.php [L]
</IfModule>

# END WordPress

Does this suggest any problems?

Nope. All the htaccess files look the same.

And when I give you a link to a resource in the Codex – I mean you read it ALL! + the related links from there.

edit: Didn’t refresh and see moshu’s post. Anyway…

Have you checked your server settings, per the Codex page? Mod_rewrite? Symlinks? Fileinfo?

Install this plugin:
AskApache Rewrite Rules Viewer and see if it reports anything unusual.

Hello,
if you change the structure and click on “save” button, there should appear a message on to that the structure has been updated.

do you get this message?

Hi Christian

Yes, I get the following message:

Permalink structure updated.

However, permalinks still don’t work properly.

Scribbler, sorry – missed your post. I installed that plugin, which tells me the following:

> Permalink: /%year%/%monthnum%/%day%/%postname%/
> Writable .htaccess file found
> mod_rewrite found
> Not using pathinfo style index permalinks
> Using mod_rewrite permalinks

This suggests everything should be working, does it not?

Any ideas guys? I’m under pressure to get this live and I’m going out of my mind. I’ve read all the relevent documentation on the site and I’m still no closer. ??

Hmm. A few months ago I would’ve assumed it was a WP issue, but they’ve fixed everything as far as I know. And I really beat the crap out my installs and haven’t had any issues with 2.5.1 yet so my guess is that its either some server configuration setting or its how the php interpreter is being used and was installed on your system.

Do you can try looking at your basic .htaccess directives like Options, DirectoryIndex, ErrorDocument, and maybe you’ll get lucky. Or you can try replacing that “Not Found” message with a phpinfo message (by setting up wordpress to output phpinfo from the 404.php) which could tell you if php is having some issues like pathinfo, and especially cgi stuff.

But now that I look at your blog, maybe it is WP.. I think I remember having the same kind of problem when trying to post in a category that is a subcategory of another category. I bet it would work if you posted into a parent category. Something is wrong when your latest posts are in your /category/archives/finally folder. Should be /category/finallly or else you will have to make pages.

Wow! I seem to have fixed it somehow, and it seems it was all so very basic. Basically, I had the category base set to /%category%/ which was screwing everything up.

Trouble is, now my category URL’s look like this:

https://www.urbaneblinds.co.uk/blinds-blog/category/doing-business-online

Is there an easy way to remove the category part of the URL?

Thanks for all your help guys.

Any ideas? ??

NinjaStory, this appears to be a common problem in WP 2.5 and I have not read of any fix for this. However, I was able to get it working on my site by changing my custom permalink from…

/index.php/%postname%/

to..

/index.php/%postname

Removing the %/ at the end got it working. Not sure why. The link that moshu posted is useless since it doesn’t address this bug. Google it, a lot of people are having the same problem when “upgrading” to WP 2.5.

The link that moshu posted is useless since it doesn’t address this bug…

I’m not certain that it is a bug, and most certainly the link moshu gave you is not useless. It clearly states:

“If you use postname as the only element in your permalinks to create a structure such as example.com/post-title, the rewrite rules may make it impossible to access pages such as your stylesheet (which has a similar format)” I think you have just found a work-around to an exception by altering the permalink structure so that it no longer bears similarities to the reasons why you should not use only /%postname%/ as stated in the documentation above. It is interesting to note that it ( /index.php/%postname), works though.