[Adam Covington]

I’m manually migrating a small WordPress intranet to Azure. I exported all Connections data to CSV on the old site, loaded Connections on the new site, licensed and installed the CSV Import extension on the new site. Today I’m attempting an import and the progress never moves beyond “Please wait…”. Based on advice from the FAQ and forum, I’m selecting “do not import” for the Entry No and Order fields, and I have deactivated almost all other plugins but the problem remains. What else can I do to make this successful? Thank you.

[Steven Zahm]

@ Adam

Sounds as if there is either a fatal javascript error occuring OR the server is responding with an invalid response.

Try this, use Chrome for the import. Load the first step of the import in Chrome (where you choose the file) and hit the F12 key. Choose you file and map as you’ve done previously. On the last step, the please wait, click the Console in the section shown when you hit the F12 key.

Are there any errors shown? If so, what are they.

Now, click the Network tab. Scroll towards the bottom. One of the last rows should be a reference to admin-ajax.php. Click that row. There could be several for you to review, but only one should be related to the import. Find that one and review the details by clicking on it. When you click on a row, the details will be shown. You’ll see the sub-tabs will be Response and Preview. These are where you will find errors.

Can you find any errors? If so, what are they.

You should also enable PHP error logging (not displaying errors). After you do an import, review the log to see if PHP is reporting any errors.

Lastly, try installing the 2.0-RC version of the of CSV Import instead. It provide more feedback and there is no need to not map the entry id.

Let me know what you learn.

[Adam Covington]

Thanks for the help. All I ever found in Chrome’s console area was, eventually, a 500 Timeout error. I removed the CSV plugin and installed the 2.0-RC version and it worked – a little too well! Apparently all of my previous attempts were still stored or queued in some fashion because the 2.0-RC version’s import resulted in six instances of many of my entries.

I scrapped this WordPress instance and deployed another, successfully using a “migration” tool this time and it transferred all Connections data for me so I didn’t need the CSV import that time. All is well, thanks again.

[Steven Zahm]

@ Adam

Good to hear you found a workable solution… That timeout error was could have been the cause if the value for PHP max execution was too low. The import does try increase this during import but host restrictions can prevent this from happening.

In regards to the duplicates… I suspect the first batch of every attempt was importing correctly while still running out of time. Both the current release version and the RC work in a similar manner. The first batch is trigger right away, then the browser, using javascript, waits for the server to send the complete message when receives tells the server to do the next batch.

[Author]

Posts