The problem about Permalinks Migration Plugin

Some people told me that they can’t redirect from default permalinks structure (/?p=#) to a new one via Permalinks Migration plugin.Revenuenets sent me a message a few days ago:

hi Dean,i think the problem that i’ve asked you previously is a wordpress 2.5 limitation,without using any plugins, wordpress itself can’t even redirect /%postname%/ to /%category%/%postname%/ .
any comments on that?

I’m woking on new version of Permalinks Migration plugin,trying to find a way to overcome that limitation and fix this issue.but i’m sorry to say,that due to another project, my free time is very limited so progress may be slow.thanks for your understand and help.

31 thoughts on “The problem about Permalinks Migration Plugin”

  1. Hi Dean

    I am also having the same problem – was very excited about being able to change my permalinks but unfortunately I had it set up as a default setting and can’t update it with permalink migration.

    I hope you will find the time to make necessary tweaks as am excited about this working properly :-)

    Victoria

  2. Hey Dean,

    I’m also struggling with this problem. I installed wordpress with the default permalink structure and can’t switch to customized on due to the bug(?).
    What is the status of your updated plugin? I’m desperately seeking for help in this issue.

    Thanks for your work!
    Cris

  3. Well, I guess I solved the problem. I just called my provider. They just offer mod_rewrite functionality with the next bigger package. So time to upgrade. ;)

    All the best,
    Cris

  4. This took me about an hour, and I thought it was broken for WordPress 2.7 based on all of the comments on this site. If you are a total newbie like me and you want to use this to change your permalinks from the Default structure, you need to put the old permalink structure as /%post_id%/ in the Settings/PermalinksMigration tab.

    It is especially confusing because Dean refers to the old structure as /?p=#/ in the above post. Anyway, if you put the old structure as /%post_id%/ it works just fine for me when you convert over to /%postname%/ or something else.

    Maybe that was obvious to other folks but not to me.

  5. The comment from Ozh helped me a lot

    Was trying to go from
    /%year%/%monthnum%/%postname%.html
    To
    /%post_id%/%postname%/ (which wasn’t working (404)

    I was trying to avoid verbose, because of slight performance differences.

    /%postname%/%post_id%/ does work

    /post/%postname%/%post_id%/ works

    Even /%post_id%/ on its own works

    But what I ended up with was….

    /%post_id%/%postname%.html

  6. I tried “putting the old structure as /%post_id%/” and it did not work for me. I’ll look at Scott Yang’s option again…

  7. I am having problems with the permalink structure for a site i built. I am getting this tructure on all pages http://www.yourdomain.com/index.php/about-us

    Also, when i go to try and change the structure in the permalinks options, on each eg. it all shows http://www.yourdomain.co.uk/index.php/2009/06/sample-post/

    When i go to custom, to change i always have to put index.php in front eg. /index.php/%category%/%postname%

    Any ideas how i can resolve this. I have tried re-install the entire site from fresh, but still the same. Could it be a server problem.

    Thanks

    Liam

  8. I successfully installed this. The only problem is that the link (at the bottom of the blog page) “Older Enteries”is not functional and it is difficult to go to the next page of blog posts. Please guide urgently!!!

  9. I have been trying to get the permalinks to change from the default setting in wordpress for over two days without any luck. My wordpress is hosted on an IIS server.
    I added the .htaccess file aswell.

    What more should I be doing. Thanks in advance

  10. Dean, I’m using your plugin, it’s great, migrated from ugly to %post_title% and works great. But the problem is, redirects are very slow. It takes around 1-2 seconds per redirect. Is there a way to accelerate this?
    Does your plugin use WP-Supercache for redirection (i think ur plugin hits databse everytime). I’m not sure it does.

  11. i recently installed this plugin in my site

    everything worked but google is unable to index my website it is showing error

    “HTTP/1.1 301 Moved Permanently
    Date: Thu, 22 Oct 2009 13:02:33 GMT
    Server: Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.5
    X-Powered-By: PHP/5.2.5
    X-Pingback: http://software-updated.com/xmlrpc.php
    Location: http://software-updated.com/adobe-photoshop-cs4/9
    Content-Length: 0
    Keep-Alive: timeout=15, max=100
    Connection: Keep-Alive
    Content-Type: text/html; charset=UTF-8″

    help me out

  12. Thank you so much for this plugin! :)  It works great for all my posts that were in my blog folder. How do I set up more than one 301 redirects, I have some posts that were in different folders.

  13. Is there still a bug with this plugin. I would like for my permalinks to have some words in them instead of just  p=#. I don't know if it is better for SEO but it seems like it would be. I am just afraid of messing something up or makng my site/articles load any slower than they already do. I have lots of links from bit.ly, twitter and my facebook fan page that I don't want to get messed up.

  14. I have a simple suggestion for a workaround to the /?p=# problem. After the if clause that starts on line 51 of "deans_permalinks_migration.php" add the following else:

      else {
          if(isset($_GET["p"]) && is_numeric($_GET["p"])) {
              $permalink = get_permalink($_GET["p"]);
              if(!empty($permalink)) {
                  header("HTTP/1.1 301 Moved Permanently", TRUE, 301);
                  header('Status: 301 Moved Permanently');
                  header("Location: ". $permalink);
                  exit();
              }
          }
      }

  15. thank you, plugin running well on my website. Initially there is an error, many dead links. In fact I already activate and deactivate some plugins, including the wpsupercache and xml google sitemap

    turns out if you first activate this plugin, try a few steps I had done.
    turn off wpsupercache, delete cache there and switch back
    Generate reset google sitemap xml (if using this plugin) manually
    wait a few minutes and then try to re-examine the links to your website.

    When I think of this plugin does not work perfectly, I use the broken link checker, and no reported errors. So I conclude this problem with the cache systemnya..
    thanks, i hope this is will help anybody had a same problems

  16. Useful plugin, I use it on many sites that I set up permalinks "wrong". The only flaw, like you mentioned is changing from /%postname%/ to /%category%/%postname%/
    But that is very minor and I can live with that

  17. Hi Dean! Thanks for this! I have a question about my subdomain, it used to be in a subfolder and I transferred everything to a subdomain, the change affected the permalinks of course but I wonder it the plugin would help…I had it activated. Thanks!

Leave a Reply

Your email address will not be published.