mikem42

OK, realised my error and hadn’t ticked the ‘Add Drop Table’ option on exporting. So I did all the above, changed the URLs (testing them to make sure the new absolute URLs linked to the right files or locations, and they did), reimported and despite a “success” message, I realised that looking in the wp_options table, the original ugly URLs were still there!

Why would these values not have overwritten the old table values properly, despite them apparently dropping the old data? Is there an easy way of doing this, or do I need to start with a fresh db, something I’m pretty nervous about?

Thanks.

HI again Samuel, I’ve just downloaded the full sql file, with Add Drop tables ticked, changed every occurrence of the ugly URL (there were several thousand) and imported the new file successfully. The site was fine, and I logged into admin again and the same ugly URLs were in General Settings, and looking back into the database again the details had all switched back also to the ugly URLs.

I reimported the “clean” file again, this time not going near the browser but looking at the wp_options fields immediately after importing – and they were the ugly URLs again. Is there some way I’m not importing the sql file properly, despite the success message? I would have thought doing this with the database would clean it all out once and for all. Should I be clearing a cache somewhere or something like that, because I don’t seem to have a wp-content/cache folder on the server.

Really wracking my brains…

Thanks so much for your prompt response, guys. Alex & Anthony – I have backed the files up, that’s why I’m using phpMyAdmin to work with the backup files (and if all goes pear-shaped I can hopefully simply re-upload the original sql file).

I was hoping to do all this without re-installing WP, seems pretty full-on for what should be a simple request? Here’s the actual problem area from the wp_commentmeta table:

— Table structure for table wp_commentmeta
—

CREATE TABLE IF NOT EXISTS wp_commentmeta (
meta_id bigint(20) unsigned NOT NULL auto_increment,
comment_id bigint(20) unsigned NOT NULL default ‘0’,
meta_key varchar(255) default NULL,
meta_value longtext,
PRIMARY KEY (meta_id),
KEY comment_id (comment_id),
KEY meta_key (meta_key)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=10 ;

—
— Dumping data for table wp_commentmeta
—

INSERT INTO wp_commentmeta (meta_id, comment_id, meta_key, meta_value) VALUES
(1, 75, ‘_wp_trash_meta_status’, ‘0’),
(2, 72, ‘_wp_trash_meta_status’, ‘0’),
(3, 69, ‘_wp_trash_meta_status’, ‘1’),
(4, 85, ‘_wp_trash_meta_status’, ‘0’),
(5, 85, ‘_wp_trash_meta_time’, ‘1292503251’),
(6, 82, ‘_wp_trash_meta_status’, ‘0’),
(7, 82, ‘_wp_trash_meta_time’, ‘1292503296’),
(8, 81, ‘_wp_trash_meta_status’, ‘0’),
(9, 81, ‘_wp_trash_meta_time’, ‘1292503304’);

Can I simple delete these lines from the sql file, or do I delete particular values? Sorry if that sounds obvious, but without going on a db training course (which I DO need to do…) I’m hoping I can get away with following simple instructions!

Thank you again…

Thank you Samuel – so is that more involved than the rewriting of the wp_options fields, ‘home’ and ‘siteurl’? Should I also need to do anything in WordPress admin/general settings?

Thanks so much again!

bump?

Thanks very much Samuel – I tried that before and it was a database nightmare, will try with a different domain for now!

Thanks Esmi – if I enter “.com/index.php” it’s still redirecting to the file-less “.com/” URL which is the index.html file. So I still can’t see the index.php page…

Tried that several times, and for some unknown reason (I hate unknown reasons…) it finally worked.

Thanks James!

Thanks for your response, James – yes, the database server’s online, I’ve checked the info in the wp-config, even got to the stage where it asked for a missing commentmeta table in the database (which I added) but despite it doing a database repair and coming back with “repairs complete”, it’s still going back to the same error message…

Hi, I’m getting the same error with this plugin –
“Call to undefined function: simplexml_load_string()”

Running WordPress 2.9.1 but on a PHP5 database (not 4 – I just upgraded this morning) hosted by 1and1. Perhaps I should upgrade to WP3.0 but not sure if that will fix it?

Thanks

Perfect – thanks.