• I have a wordpress blog on 007ihost.com (2.0.5) and I started another one on a different server: yourfreehosting.net (2.3.1).

    Now I have already posted all my posts and categories and w/e on the 007 one, and I started the 2.3.1 one to see what features they had, and it turns out the server was much better (they allowed more files)

    How do I move all my posts & categories from the older blog to the newer blog on a different server,

    ANY help would be greatly appreciated

    PS the 2.0.5 version doesnt have the Export feature like the 2.3.1 version, it only has the import feature

Viewing 8 replies - 1 through 8 (of 8 total)
  • Install the techsailor plugin on your 2.0.5 install and export the content to import into the new install:

    http://technosailor.com/wordpress-to-wordpress-import/

    Trent

    I used the phpMyadmin to export the database and then import it, after import, when you login the admin, it will upgrade the databased and it should work.

    Of course, you need to add the plugin you installed at the older version.

    Thread Starter shadowd7

    (@shadowd7)

    Thank you both,

    Trent: I tried doing that, everything was going all and well, i exported perfectly ( i have the XML file) I was going to import it, didnt work. I realized i needed to put the same plugin in I used, wouldnt load right….might have done something wrong i dono, but did it exactly the same way. ( I think if i got this to work it would fix the prob)

    edgarlin: will phpMyadmin delete old posts or just add to them? I would love to try it, if it’ll work, is there a guide or can u please help me
    Please, if u can, Email me shadowd7@gmail.com

    Thank you all, and if anyone else has other Ideas, glad to hear them

    Hi Shadowd:

    You can delete the data (original one when install) and import it, i did not have guide, just use phpMyAdmin to import the new database.

    Thread Starter shadowd7

    (@shadowd7)

    I went to phpmyadmin and exported w/e i could (figured it would be wat i needed) and i got this file (localhost.sql) now when i went to the other server I got an Error msg,

    I noticed that the Databases werent the same names (*_psp the other *_wp) so i simply changed the text in the sql file hoping it would work…..

    didnt got the same error msg
    ____________________________________________________
    SQL query:

    – phpMyAdmin SQL Dump
    — version 2.8.2
    http://www.phpmyadmin.net

    — Host: localhost
    — Generation Time: Nov 20, 2007 at 01:02 PM
    — Server version: 5.0.27
    — PHP Version: 4.3.10-16

    — Database: shadowd7_wp

    CREATE DATABASE shadowd7_wp DEFAULT CHARACTER SET latin1 COLLATE latin1_swedish_ci;

    MySQL said: Documentation
    #1064 – You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘CREATE DATABASE shadowd7_wp DEFAULT CHARACTER SET latin1 CO
    _____________________________________________________

    nothing seems to be working and im soo close to just reposting everything….

    If you could help me fix this i would be sooo Grateful!!

    but if not, better start Copy and pasting 🙁 🙁

    When I export the database, I click the “Add DROP TABLE / DROP VIEW” under structure, and the I empty the database then import the database I backup. Due to I use the original table name, so I did not change it, you need to check if you use different table name.

    Thread Starter shadowd7

    (@shadowd7)

    ok everyone Im gonna try the plugin thing one more time and then just repost it…..

    thanks anyways

    The error message points to the character encoding.

    Even though many Apache setups use latin1_swedish_cgi (is it ci or cgi?) as default encoding, I’ve been instructed to nevertheless change the stated encoding on an sql file being imported to UTF-8.
    (Take a look at the subject dbs’s encoding via phpmyadmin first to confirm that they were specified as UTF-8 before considering the above suggestion. :))

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Old server to New Server & 2.0.5 to 2.3.1’ is closed to new replies.