Why would you want to do that?
So it can resume where the other left off. I can’t get it to work without doing this.
That’s odd. I’ve changed servers, hosts etc. a number of times in the last year, and all I’ve ever done is dump the database and import back once on the new server/host; the posts start up where they left off just fine.
If you did a proper export from MySQL, I believe it should be a virtual copy of the original, so it would start where it left off. The WordPress Guides by podz are an excellent resource. You may want to do the export/import over-again following his guides.
I don’t understand why you can’t get it to work without doing this, could you explain what you mean?
Cheers,
Michael.
I just tried podz guide and tried again and it still won’t work. I’m to the point right now where I want it to work just to save me the time from reposting everything, editing each timestamp and then retagging them.
WordPress won’t acknowlede that it should start where the db leaves off…thats the problem.
Someone correct me if I’m wrong, but I beleive the post ID’s are assigned by MySQL, not WordPress. The tables just use the auto_increment feature in MySQL, so this may be a MySQL problem and not necessarily a WordPress one.
So when you do the full export, exactly as podz’s guides suggest and then import, also following his guides, what happens exactly?
Michael.
I go to post and it will give me this error:
WordPress database error: [Duplicate entry ‘0’ for key 1]
INSERT INTO wp_postmeta (post_id,meta_key,meta_value) VALUES (‘0′,’_pingme’,’1′)
WordPress database error: [Duplicate entry ‘0’ for key 1]
INSERT INTO wp_postmeta (post_id,meta_key,meta_value) VALUES (‘0′,’_encloseme’,’1′)
Warning: Cannot modify header information – headers already sent by (output started at /home/virtual/site202/fst/var/www/html/wp-includes/wp-db.php:102) in /home/virtual/site202/fst/var/www/html/wp-admin/post.php on line 59
Now, it will end up posting, but I’m not sure if it is overwriting it or what. However, it is annoying and unwanted so I’d rather get it fixed than have it just exist.
Now, it should be noted that I did have to change mysql editions with my export. However, I don’t think this has anything todo with that, but what do i know 😛
