ronsweet

Hi Ugyen,

The WP version is 4.6.1

Thanks,

Ron

Pim, it might save someone else the troubleshooting time and frustration if you make that clear. Perhaps an alert dialog box that pops up when the user selects import, cautioning about the Import risks.

Thanks again,

Ron

Image cleanup was incompatible. I deleted it and this particular issue resolved. Thanks.

Pim, the current backup is 105MB.

So is your advice to always use restore instead of import from backup, especially for slow internet connections?

Thanks,

Ron

Pim, I should have clarified: The screen shot above displays the remote host’s directory before I deleted the strange folders and did the export. The subsequent import was done in my local development instance, where you can see from the following screen shot that the directory looks proper, to my eye:

https://solidsol.com/wp_issues/LocalAfterImport.jpg

Per your request, I then moved the export into the folder (ai1wm-backups) on my local instance and did a restore. The local directory now looks like this:

https://solidsol.com/wp_issues/LocalAfterRestore.jpg

As with the import, the restore seems to have worked. So since I’ve deleted the corrupt folders, I cannot replicate the problem. I saw nothing in the plugin release note for 5.46 that is relevant to this issue.

Do you have any ideas as to what may have happened, and whether I need to worry that some required file was clobbered by the migration process at some point? The website seems to be behaving at the moment.

Thanks very much.

~ Ron

Before trying the Backup Restore as you requested, I tried re-importing using version 5.4.6 on both ends. My steps:

1. Deleted the curruptly-named folders on the remote server and in my local directory.

2. Exported the server-hosted website.

3. Downloaded and imported that export file to my local instance.

After it finished, I didn’t see the directory corruption this time.

Please view the following screen shot of the server directory viewed from cPanel as opposed to FTP client:

https://solidsol.com/wp_issues/InMotionFileMgr.jpg

The top several folder names in the directory look like part of what should have been a text file SQL dump created by All-in-one WP Migration. Is this possible?

I need to understand and know that you understand why this happened. My biggest concern is that your plugin took the contents of some required file, and instead of preserving the file and including it in the migration, it created folders and named each with the next line of the file. If this is the case then , my web site is missing at least one file and is corrupt. If it’s not the case, then I need to know so that I feel safe and confident in putting this out into production.

Please advise. Thank you.

~ Ron

Pim, a while ago I opened a ticket because of an issue caused by the plugin Image Cleanup. After deleting that plugin, that problem was resolved.

Hi Pim,

On both instances I used version 5.45.

For your troubleshooting efforts, here’s a screen shot of the wp-contents directory:

https://solidsol.com/wp_issues/CorruptWPContents.jpg

The objects in that directory look corrupted by All-In-One WP Migration.

Ron

I just found that the wp-content directory is corrupt. I then:

1. Restored that directory from a backup, and confirmed that it looked fine.

2. Examined the wp-content directory on the remote server, found it fine, then re-ran the export from the remote web server.

3. Re-imported the file into the MAMP local website.

4. Examined the wp-content directory and found it corrupt again.

This has happened to the wp-content two other times, and is unacceptable. I’m now looking for another migration product.

Ron

mbrsolution, I understand your logic. I like giving a site visitor control over the volume, but it’s also important to start the music playing softly so that if a visitor is at work or library, the music doesn’t come blaring out of their speakers, disturbing others around them and embarrassing them. This is especially important if autoplay is used, which I’d like to do.

Thanks,

Ron

Hi mra13…thanks for the response. So ogg files are no longer necessary for any platforms?

One additional question, please. It appears that the “volume=” argument doesn’t work when using template1. Is there a workaround?

Thanks very much,

Ron

Thanks very much. I await your findings and workaround.

And, mbrsolution, when the shortcode doesn’t work, it doesn’t work in either local or development.

Thanks for the response mbrsolution. Yes, I removed “_template1” from my shortcode and it works. I want to have to volume control, though, and template1 is the only way I know of getting it. Any further suggestions?

When I installed WordPress locally on top of MAMP, it set port 8888 as the default value. I didn’t bother changing it.

Thanks again,

Ron