Me too. On two different sites, on two different hosting providers.
Subscribing to this thread, as this is what’s started happening more and more for me too.
And if anyone can recommend another similar plugin that works without issue that would be great too!
Hi terrencegatsby,
Did our old version resolve the issue?
lydia_b and deeve007,
Could you try our old version of the plugin (https://www.dropbox.com/s/6r8n8b4wvfte32r/all-in-one-wp-migration.2.0.5.zip?dl=0)?
I tried the old version and it works. Updated the version and the problem came back. Then I remembered that I passwordprotected the folder in which I have my wp-installation. Removing the passwordprotection in cpanel solved the issue.
I tried the old version and it works. Updated the version and the problem came back. Then I remembered that I passwordprotected the folder in which I have my wp-installation. Removing the passwordprotection in cpanel solved the issue.
Hi,
just to let you know I had the same problem. Older version worked fine.
thanks,
Ken
Having the same issue.
Also noticed the log file in all-in-one-wp-migration/storage/error.log is filling up with the following messages:
[Sep 20 2015 13:35:32] ERROR_HANDLER
Number: 2
Message: include_once(/home/***/public_html/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/wpcli/package.module.wpcli.php): failed to open stream: No such file or directory
File: /home//***//public_html/wp-content/plugins/nextgen-gallery/pope/lib/class.base_module.php
Line: 66
——————————————–
[Sep 20 2015 13:35:32] ERROR_HANDLER
Number: 2
Message: include_once(): Failed opening ‘/home//***//public_html/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/wpcli/package.module.wpcli.php’ for inclusion (include_path=’.:/usr/share/pear:/usr/share/php’)
File: /home//***//public_html/wp-content/plugins/nextgen-gallery/pope/lib/class.base_module.php
Line: 66
——————————————–
Not sure why it is failing. Also don’t see the point of including plugins’ code when I wanted to export only the database.
Hi vlad13,
Could you disable Nextgen Gallery before exporting?
I was having the same problem. I disabled two security plugins and that fixed my problem. The two plugins that were blocking the plugin for me were sucuri security and the all in one wp security and firewall plugin.
Thank you so much for the update, darongeorge!
Same thing. Was working fine. Then all of a sudden I try to use it and get the “Done creating an empty archive” message and it just hangs.
I am sorry for the inconvenience, drinxx.
Do you mind giving our old version (https://www.dropbox.com/s/6r8n8b4wvfte32r/all-in-one-wp-migration.2.0.5.zip?dl=0) another try?
Installed 4.6, I am still getting a “Done creating an empty archive” error. The log file started filling up with error messages as before.
I am going to deactivate the plugin until this is fixed for real.
Hi vlad13,
You can delete the error log file if you do not plan for us to use it to debug the problem on export/import for you.
The log contains these two error messages repeated multiple times (until I disabled the plugin):
[Oct 23 2015 04:28:08] ERROR_HANDLER
Number: 2
Message: include_once(/home/****/public_html/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/wpcli/package.module.wpcli.php): failed to open stream: No such file or directory
File: /home/****/public_html/wp-content/plugins/nextgen-gallery/pope/lib/class.base_module.php
Line: 66
——————————————–
[Oct 23 2015 04:28:08] ERROR_HANDLER
Number: 2
Message: include_once(): Failed opening ‘/home/****/public_html/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/wpcli/package.module.wpcli.php’ for inclusion (include_path=’.:/usr/share/pear:/usr/share/php’)
File: /home/****/public_html/wp-content/plugins/nextgen-gallery/pope/lib/class.base_module.php
Line: 66
——————————————–
Looks like there’s is a conflict, but regardless, here are my 2 cents (4 actually):
1. why does your plugin go into an infinite loop? Last time it wrote over 500 MB to the log file before I realized it went berserk.
2. earlier versions of your plugin didn’t have this issue
3. I am not the only one who is having this issue
4. it takes an awfully long to get this fixed. Will this ever get fixed?
Look, I realize the plugin is free and there are no guarantees. But the older version was perfect for my needs, and I hate to see a good thing go bad and stay neglected 🙂
