How do i clean up my urls/permalinks?

dv-design – I just got the answer. You do need to create a .htaccess file with this code in it:

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

# END WordPress

When you create your htaccess file in Notepad, don’t have your .txt extension selected. Rather have the All files from the drop-down type in Notepad selected so when you save your htaccess file, it will automatically have the .htaccess extension. Then upload this file to your WordPress directory on your server, and that should allow your new permalink structure to work, and your page links will come back. Someone just told me how to do this, and I did it, and the pages automatically linked back up again! Good luck.

Got it working by using the directions posted here:

Poster alamster near the bottom of the post.

I’ve just realised a mistake i made in my last response, when i was referring to uncommenting a line in the conf file, i did in fact mean the rewrite module, as indicated in that thread.

Looks like i was on the right track .. the post you followed is pretty much precisely what i’ve said above (my error most likely didn’t help though)..

Happy you found your solution though … ??

Still trying to resolve my issue too and wanted to check my htaccess before trying anything else.
ja2006 showed this code above:

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

# END WordPress

But mine is this: (following the super cache codes, so I’ll start with the supercache code end):

# END WPSuperCache

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

#END WordPress

So mine is messed up? It’s missing the wordpress name in there. And, should it be written in the htaccess file prior to the WPSupercache codes, or after?

Also, just to clarify the location of mine is here:
root/myurl.com
Then there’s the 3 directories for WP, with the files below including the htaccess file.
wp 2.9.1 is what I’m running, if that makes any difference. Thanks.

t31os_
Moderator,
I wanted to also thank you for your offer of help in this thread, and I haven’t yet tried what you suggested since I figured I better first check to see if my htaccess file codes are correct or not. (Above) Thanks again.

Assuming the htaccess is in root along with WordPress the above looks exactly as it should be.

You’d only have a directory name in the rules if you had WordPress installed in a sub-directory and the htaccess remained in root, else if the htaccess is in the sub-directory along with WordPress it would look the same as above.

Thanks again t31os,
I didn’t get a chance to take a look at this again until now. Okay, so it appears my htaccess file code and location is correct, and I haven’t had other issues that would be caused by the htaccess that I know of. So, I’m ruling that out.

I did a new blog post to see if the problem still occurs, but I’m confused about what you said in one of the posts here:

When you say it ends up in the old format, where are you actually looking at in the DB?..

If you’re referring to post_guid in the posts table, that’s normal behaviour and the guid will show a PHP query string style URL, eg. https://example.com/?p=1 … it’s suppose to …

When I examine the post_guid in my database, this is what it shows for some of the blog post titles. As an example, some are in this permalink format under “guide” as this:
https://www.myurl.com/?p=998

All the draft posts are in that format. But then some blog posts, once their published are in the pretty permalink structure like this:
https://www.myurl.com/2008/04/30/post-name-is-here/
and some are not! Any new blog posts I publish are in this format:
https://www.myurl.com/?p=998

Again, just to clarify, my blog had been upgraded from 2.7.1 to 2.9.1, but I’m not sure if that was when the problem occurred, or due to a hack, which was cleaned up prior to the upgrade, but there may have still been some bad codes remaining when the upgrade was done.

In order to correct the problem in my database, I’m really hoping to not have to reinstall a bunch of files, if possible. Somewhat fearful I might create another problem by doing so, if I goof! Thanks again for the help.

Just to be clear, the guid for published and draft posts or pages will always show in the query string format, ie. example.com/?p=1 (the same is true in wp 3.0).

If the final URL, ie. what you see when the post/page is published .. is showing the guid URL instead of the pretty version, i can only guess that it’s a bug/error of some kind, as to what the cause is, your guess is as good as mine.

Does this happen with just posts or pages to?