New answers tagged migration
The easiest way around this is probably to reset the Admin password on the old Database. If you have PHPMyAdmin or a very similar DB admin interface, do the following: Import the old database. Open the user's table, usually called 'wp_users'. Find the user you wish to change the password for, and replace the contents of the 'user_pass' field with a plain ...
Using the WordPress XML export doesn't work in every case. Especially if you have to deal with plugins. I had the best results if I first installed the theme and all plugins in the network, created a new site, activated theme and plugins (in case they create data base tables) and then import the WordPress XML. For NextGenGallery it didn't work, though. I ...
Ended up taking a different approach - I exported all the content I had already created so I didn't lose it, used the WB Migrate DB Pro plugin to import the content I wanted to carry over from my old site, and them imported all the new data again. A bit roundabout but effective!
I'm assuming you have an sql file that you're uploading? If so, open that file in a text editor such as Notepad. Search for 'user_login', and somewhere nearby that you should see something similar to 'INSERT INTO wp_users (ID,user_login' etc. On the next line after this, you should see something like (1, 'admin', 'password' where 'admin' is the admin ...
You should use some migration plugin, e. g. Migrate DB, because some file paths and URLs are serialized in database and it's not enough to change just siteurl and home. Migrate DB seamlessly do the job.
I just understood what happened: The custom widgets were using short tags (<?) to split up the HTML output, which directive (short_open_tag) is disabled by default in the production environment. Problems like this are a pain to spot and I can do nothing but laughing thinking what we tried to understand the issue.
Top 50 recent answers are included