Changing from default permalinks or standard permalinks to fancy permalinks or pretty permalinks with SEO (Search Engine Optimization) and other things in mind:
If you were using default permalinks, leave the "Old Permalink Structure" on Dean's plugin setting page blank and click the update button. It will return a single slash mark.
Then go to WordPress Settings and then Permalinks. Click on any of the other choices besides the default, and the "Custom Structure" box will automatically populate. You can then change that to whatever you want. See the WordPress Codex: Using Permalinks for ideas on tags. You can leave off the trailing slash mark too. I did. I took it a step further. I'm now using /%year%/%monthnum%/%day%/%postname%.html
I like the extension (.html), because saved files are clearly associated with the default program that way. Most browsers will append .htm or .html automatically, but adding it just removes ever having to think about it again. I have had files save without extensions before, probably when I was in a hurry and taking too much for granted. I don't trust opening those, so I end up running scans on them when I go back to them perhaps months later. By adding the extension, it removes wondering later and the added hassle.
Dean's Permalinks Migration Plugin all worked for me the first time, but only because I thought about it for a while and read some of the early comments on the author's plugin page. If it doesn't work for you, there could be many reasons that have to do with your hosting service and whether or not you are on a Microsoft server rather than UNIX/Linux. You'll have to do some reading on it.
.htaccess and Giving WordPress its Own Directory While Leaving Your Blog in the Root Directory
By the way, the change was appended to my .htaccess file rather than overwriting it. I had to copy it to "/" from "//", because I installed wordpress in a subdirectory named wordpress. "Giving WordPress its Own Directory While Leaving Your Blog in the Root Directory."
WP Super Cache and GoDaddy
So, why did I want to do this? For one, supposedly, the words in the title of the post also being in the URL (page address) helps as being another location of keywords. However, that wasn't enough to get me to change. The fact is that WP Super Cache WordPress plugin doesn't work with the default permalinks (?p=1030 for example). The reason I want to use WP Super Cache is because it goes over the top of the WP-Cache plugin I've been using successfully for many months now but takes WP-Cache to the next level. It serves up pages while reducing steps back and forth to and from the server php-engine. I need all the speed I can get and to reduce overhead since I'm on the most affordable web hosting out there I think (GoDaddy).
By the way, I've seen GoDaddy rapped left and right in my travels around the Web. Frankly, I've had zero problems, and GoDaddy is my fourth hosting service if memory serves. If you will read their help files, you can usually find the answer you need. Of course, they aren't going to let you nose around root as a super user if you're just on the economy, virtual, shared server, which I am as of the date of this writing.
Freedom of Political and Religious Speech
Let me say something else on GoDaddy's behalf. They appear to be believers in freedom of political and religious speech, which is a good thing. It is up to the individual to exercise self-control and to have a working conscience. It is true that there are people out there who say things that are deliberately designed to lead others off into pain and suffering that awaits, but if all of those people were silenced by coercive and violent means, which human being would be capable of deciding exactly where to draw the line on when to stop silencing people? As Jesus says, only God is good (perfect enough to know), and God judges no man or woman. Did you know that? Most people think God judges and condemns. That's the other spirit.
Back to WP Super Cache
Anyway, back to technology (which is only as good as the unselfish pursuits for which it is employed), I want to use WP Super Cache. However, I had to map out the whole plan before starting down this path, because GoDaddy presents a special case concerning WP-Cache on which WP Super Cache is built. So, I turned to the same place where I turned the second time for WP-Cache and that's givveronline.com.
. Ramblings of a Bored Geek. February 17, 2008.
As I mentioned As I mentioned in CLEANING UP AND SPEEDING UP WORDPRESS AND MORE, Tuesday, September 16, 2008, I had manually made all the changes to WP-Cache but had that work stepped on. I didn't have a backup back then, and when I went back out onto the Internet in search of the info I had used [ , by Brad. Online Dating Guide & Blog. September 8th, 2007.], I cane across givveronline.com where everything was all done and served up as a special version of the WP-Cache plugin just for GoDaddy. Well, he ended up doing the same thing for WP Super Cache.
If you're on GoDaddy and tried WP-Cache only to get Internal Server Errors or blank pages every other time you tried to access a page, try GoDaddy WP Super Cache. Read WP Super Cache, by Donncha first though. [UPDATE!] You better finished reading this though to save yourself a lot of trouble.
I downloaded the GoDaddy WP Super Cache. I did everything I was supposed to. It loaded. The settings page came up fine. I set things up and saved. The settings held. I thought everything was fine. However, when I had looked around on the site to see if everything was truly fine, I remembered that being logged in, I wouldn't see the speed-up. So, I opened Safari to go to the site so I could stay logged in on Opera. I was also ready to look at the cache via FTP. Well, the cache stayed empty.
I looked at the code. Sure enough, the GoDaddy fixes were there. I thought that maybe since the version was old, I'd just down load the latest one and make the changes myself. So, I cleaned everything out. I even emptied the .htaccess file after backing it up. I downloaded the latest version of Super Cache. When I went to make the changes, I discovered the GoDaddy fixes were already there as part of the plugin. That's good, because now I don't have to worry about updates overwriting the patches. Now, let's see if it will work.
Supercache Subdirectory Wasn't Automatically Created
Well, after going through everything suggested step-by-step, I finally moved the .htaccess up one directory level because I run WordPress from a subdirectory but there is an old configuration issue that I've never backed into to figure out. It would be too longwinded to explain here now. Then I manually created wp-content/cache/supercache/. The supercache subdirectory wasn't automatically created by the plugin. It works now.
However, it isn't compatible with the Theme Switcher. The Theme Switcher though is the old version. The newer one might work. I'm planning to try it out.
I slept on that last idea. I was tired when I wrote it. In thinking about it a little, there isn't a way that the plugins as written will work together. A switched theme would require a cache directory-tree of its own.
Theme Switcher Reloaded
I tried the newer theme switcher just to see. It did work as advertised, but the cache wasn't overwritten by the different theme choice. So, no more public theme switching for a while anyway.
Next, I worked on the Asirra plugin, which is an anti-comment spam plugin for WordPress by Microsoft. It's a good idea and worked for a while. Today though, it gave me a bunch of invalids, even though I had selected the proper images for sure. It broke my theme too (too wide at lower screen-resolution settings). I try to avoid horizontal scroll bars appearing for people who use lower resolution. About 10-15% of the site's visitors use low-res.