chewoutloud

I’m really baffled now. I created a new installation of WP in a /stage subfolder. After getting that up and running, I had a new fresh blog. I tried importing my export file and it still failed. I went to WordPress.com and created a new test blog with a single post and exported a backup file. I tried imported that little backup file into the new WP instance and it failed with the same errors.

The only thing I can point my finger at is the 3.5.1 version. Surely the importer can’t be incompatible with this version or else someone else would’ve already caught it, right?

Sorry, I can’t help, but I’m also having problems importing from a wordpress.com XML backup and I’m beginning to wonder if its due to 3.5.1. The backup file worked when imported in 3.5, but importing the same file in new instances of 3.5.1 results in an error.

I was browsing in the file manager and noticed that I have a public_html and a www directory, both containing the same files/folders.

I changed the name of the plugin directory in the www directory and this seemed to work because the admin UI showed that I didn’t have any plugins.

Was I also supposed to rename the plugins directory in the public_html directory also?

Thanks for the suggestions, but all I’m getting is frustrated. I’ve tried:

– Reverting back to the default Twenty Twelve theme.
– Deactivating all plugins via the admin UI.
– Deactivation all plugins by renaming the plugins folder in wp-content.

Nothing worked…still same error.

I didn’t try renaming the mu-plugins folder…where is that?