The problem I was experiencing with the All-in-One WP Migration WP Plugin was restoring the backup file it generates when this was greater than 64MB. It has no problems creating the backup file, it is just when I wanted to restore from it when it was greater than 64MB that it was problematic.
There are some workarounds which may help you. These workarounds worked at the time of writing this. This may not be the case in the future.
Although I could buy additional extensions from the All-in-One WP Migration WP Plugin developers this was not something I was willing to do.
There was nothing in the description for the plugin which indicated that the premium version of the plugin is required for restoring websites. Furthermore there was nothing about the size of the backup file. Therefore I did not expect this problem when the backup file the All-in-One WP Migration WP Plugin generates was larger than 64MB.
Fair enough, the All-in-One WP Migration WP Plugin developers want people to buy additional extensions so that they can continue to work on the plugin. After all, it does cost time and effort to develop a WordPress plugin. And it can cost more time and effort to support it and to update it with new features and to fix bugs.
I do think that they could be more honest and forthcoming about these limitations before people want to restore backups or import websites.
The freeium version of the All-in-One WP Migration WP Plugin can be affected by the maximum file size value inside of WordPress, which in turn is related to the webserver that WordPress itself is using. This in actual fact is an artifical limit imposed by the developers of the plugin.
The freeium version of the All-in-One WP Migration WP Plugin will happily save your website for you. However if the size of the backup file that it generates is greater than the maximum file size value inside of WordPress, it will not restore successfully.
I believe that if the backup file is greater than 512MB, the freeium version of the All-in-One WP Migration WP Plugin also will not work, no matter what the maximum file size value inside of WordPress is.
At that stage you need an alternate plan that you know that works. Here’s a post on one way to copy one WordPress website to another I wrote that may help. Those options are highly technical and dependent on the plugin’s developers not changing existing functionally within the plugin itself.
They are a third party and this is something that could happen, either by accident or by design. So this is not really a long term solution for me. Even with regular testing I would not be really sure that this solution would work for me when it really has to.
Especially when other free WordPress plugins have similar backup and restore functionally that simply does what I expect it to do.
Your web host may be enforcing the the maximum file size value inside of WordPress value to be 64MB. This may be a limitation imposed by the webservers that your web host uses behind the scenes or it may be an artifical limit imposed by them. If the All-in-One WP Migration WP Plugin generated a file greater than 64MB, you can’t restore it successfully yourself unto a website with this maximum file size value set to 64MB.
At least one web host has a workaround which works.
This involved opening a Hosting Support ticket with your web host. And seeing do they come back with a solution. At least one web host has a solution.
I was able to use this approach with the web host I was using during January/February 2021. And it worked. The size of the backup file generated by the All-in-One WP Migration WP Plugin was between 64MB and less than 512MB. I was not able to use that file. I simply put that file in a place where my web host could grab it at Dropbox. Then support at my web host was able to use that file and restore successfully from it.
I learned about my workaround five later. Workaround five would have worked without the need for me to involve any hosting support.
If you are using NameCheap’s EasyWP Managed WordPress hosting, know that in March/April 2021, the maximum file size value inside of WordPress value was 512MB. The size of the backup file generated by the All-in-One WP Migration WP Plugin was between 64MB and less than 512MB. I was able to use that file to successfully restore a website.
EasyWP have more details about this approach here.
My fourth workaround was to look at other WordPress Plugins that provide save and restore functionally. This was when I came across the UpdraftPlus backup/restore WordPress plugin. This uses chunking technology behind the scenes to overcome file size limits. It also has some other neat functionally which I like.
My fifth workaround was to look at a way to actually use an earlier version of the plugin with a documented coding change.
The documented coding change is not actually required if the file that the plugin generates is less than 512MB.
This may be an option to look at if you are in the process of restoring a backup where the file itself is too big.
This solution is not guaranteed. This solution involves using an earlier version of the plugin. WordPress include the following warning about using previous versions of plugins.
Previous versions of plugins may not be secure or stable. They are not recommended for use on production websites.
Artifical Fictional File Size Limit Added
The developers of the plugin inserted an artificial fictional file size limit into the code itself around version 6.77 of the plugin released I believe, between June 2018 and October 2018.
People are angry, frustrated, annoyed and have a range of other negative emotions when they discover this file size limit when they need to restore in anger as they would not have expected this issue to come up.
True enough, people should be testing and confirming for themselves that the plugin works in the way that they expect. However, most people would assume that if the file saved successfully, it should also restore/import successfully with no issues.
After all, the information about this plugin at WordPress.org has the following in its description, even about three years or more after the artifical fictional file size limit was imposed.
BYPASS ALL UPLOAD SIZE RESTRICTION
We use chunks to import your site data. Most providers set the maximum upload file size to 2MB. As the file restrictions are only applied to each chunk, webserver upload size restrictions are bypassed by keeping the chunks under 2MB to easily upload your entire site.
Source: https://wordpress.org/plugins/all-in-one-wp-migration/ on June 13, 2021
To my mind, this implies that there would be no problems regarding the size of the import file. Yet they are still including this three years after imposing an artifical file size limit on the size of the import file.
The next problem is that version 6.77 is no longer available within the WordPress depository. Go to:
Page down to the bottom of the page, then click on the “Please select a specific version to download”.
Version 6.77 is not on that list.
How I Managed To Get Version 6.77 in June 2021
There is a website on the web that archives websites called https://web.archive.org
This website takes snapshots of websites every now and then. It just happens that one of these snapshots during 2018 has version 6.77 in its snapshot.
I grabbed version 6.77 of the plugin on June 13th 2021 from this snapshot. And it seemed to work for me with no issues. I did not actually have to change a line of code in that version as my website backup using the plugin was 156MB.
I believe that if my website backup using the plugin was above 512MB I would need to change one line of code in version 6.77 of the plugin.
Here’s how to grab version 6.77 of the plugin.
Go to https://web.archive.org
Enter https://wordpress.org/plugins/all-in-one-wp-migration/advanced/ into its search engine.
Wait a few moments for it to display its Calendar. I opted to find and use the oldest version of version 6.77 that I could find here.
After doing a bit of rooting around, I discovered:
- The snapshot taken on June 17th 2018 referred to version 6.70. The list of previous versions does not include version 6.77. It couldn’t because it hasn’t been released yet. And time travel has not been invented yet!
- The snapshot taken on October 30th 2018 referred to version 6.79. The list of previous versions includes version 6.77. This was the only snapshot that actually includes version 6.77.
Select 2018 from the calendar. Then click on the October 30th, 2018 date, then click on the snapshot it captured that day.
This goes to the following URL:
Page down to the bottom of that page.
Within the Previous Versions section, click on the arrow beside the words “Development Version”. This displays a list of available versions. Click on 6.77 on that list.
This displays the following:
Confirm that 6.77 is displayed to the left of the download button. Then click on the download button.
For your convenience, you can use the following direct link instead:
Once the all-in-one-wp-migration.6.77 zip file is on your device, put it in a suitable folder. Consider having a “Do Not Delete WordPress Plugins Folder” and copying it in there also. Just to be on the safe side.
Assumptions and Disclaimers
I grabbed this file from this archive because I assume that this archive is trustworthy. I assume also that it wouldn’t change the zip files it grabbed back on October 30th 2018. I assume that the developers of the plugin did not modify that zip file before the snapshot was obtained.
These are assumptions which may be false.
This version retrieved from this archive has not been tested on the latest version of WordPress. This version retrieved from this archive may not be secure. This version retrieved from this archive may not be stable.
Just saying. 🙂
The Process On The From Website
Save your from website using the current version of the All-in-One WP Migration WP Plugin.
If everything in a later stage is not restored successfully, you might need to consider repeating this process, except that you save your from website using version 6.77 of the All-in-One WP Migration WP Plugin. A potential reason is that the developers of the plugin may put in changed logic in future versions of their plugin to save things in a different way that version 6.77 does not know about.
Download the file it generated to your computer. Note the size of it. If the size is greater than 512MB you will need to change a line of code in a later step.
The Process On The To Website
Install WordPress on the To website if WordPress is not yet installed. I would recommend that its version is the same as the version of WordPress on your Original website.
Install version 6.77 of the All-in-One WP Migration WP Plugin. You can do this by going to your WordPress Dashboard, then Plugins, then Add New, the Upload Plugin, Choose file (from where you saved it on your computer assuming you grabbed it earlier), Install Now, Activate Plugin.
The list of Plugins is redisplayed. You should see the All-in-One WP Migration WP Plugin included in that list with a hint to upgrade it. Do not upgrade it and ensure that the automatic update value for that plugin is not enabled.
If the plugin is updated by you manually or updated automatically, the restore process will not work if the file created by the plugin is too big. In that case, deactivate the plugin, delete the plugin, and re-install version 6.77 of the plugin again, and disable the automatic updates for this particular plugin.
If the from file is greater than 512MB, you need to change a line of code
Version 6.77 of the plugin will usually restore successfully if the file it imports was generated by the plugin and it is smaller than 512MB. If the file however is greater than 512MB, you have to apply a one line change.
On the to website, ensure that you have version 6.77 of the plugin installed and activated. I believe that the developers of the plugin at version 6.78 and above, have put in additional functionally to prevent this solution from working.
Using the WordPress Dashboard, Select Plugins, then Plugin Editor, near the top right you see a “select plugin to edit” with a currently selected plugin, Click on the “down arrow” to the right of the selected plugin, See a list of installed plugins, Select the “All-in-One WP Migration” from the list, Click on the “Select” button.
This displays source files for the “All-in-One WP Migration” plugin. On the right, there is a list, click on the “constants.php” file. You should see something like the following:
You should now be at the top of the constants.php file for the All-in-One WP Migration” plugin. And that should look like the above.
The terms of the software licence are displayed. They are actually highlighed above in my screenshot. You are allowed to legally modify the code. Just making this point, in case it was something on your mind.
Now page down to line 284 of this source file.
Line 284 defines the maximum file size.
- 2 << 28 is an alternative way of specifying 512MB
- 2 << 27 is an alternative way of specifying 256MB
- 2 << 29 is an alternative way of specifying 1GB
- 2 << 30 is an alternative way of specifying 2GB
- 2 << 31 is an alternative way of specifying 4GB
- 2 << 32 is an alternative way of specifying 8GB
Change that number 28 to a number of your chosing.
The number needs to be big enough to cater for the size of the import/backup file that you are going to use.
The following instructions assume that the limit is to be 2 GB ( 2 << 30 ). So in this case, the 28 changes to 30.
Step 1: Change the 28 to 30 on line 284
Step 2: Click ‘Update File’
WordPress performs the update and if successful, displays a file edited successfully message.
Then you should in theory anyway be able to import your “big” file. Jump to Importing “Big” File Using Version 6.77 section.
If the from file is less than 512MB, there is no need to change that line of code
In my case, the current version of the plugin limits the maximum file size to be 64MB. The size of my import/backup file is 156MB.
Using the current version (version 7.44) of the plugin, I cannot restore from backup as this is now paid functionally.
Using the current version (version 7.44) of the plugin, I downloaded the backup and then attempted to use “import from file”. I cannot import this file. Because 156MB is greater than 64MB.
Importing “Big” File Using Version 6.77
However using version 6.77 of the plugin, I can import this file. Because 156MB is less than 512MB. And I did not have to apply the above code change as there is no need.
If your file size is greater than 512MB, you need to do the code change documented earlier in this post! Of course any references to the 512MB file size will be different in your case. I supply the screenshots here as an aid for you.
After it uploads my copy of the 156MB file from my computer to its folder inside WordPress I get the following screen:
I then clicked on the Proceed button. It does some processing, and then the following screen is displayed:
I clicked on option 1 of the above screen and saved the permalinks structure twice. Then the job was done.
After looking around my website, it appeared to me that the restore was successful.
Here Are Some Recommendations
Thank you for reading this article. I hope you found it helpful. Here are some recommendations for the next time you are looking for a domain registrar or a webhost that I hope you’ll also find helpful.
Hey you know what? I know about this based on my online experience. You came to my article because I have some knowledge and authority on this subject. I hope that I answered your question for you. But also here let me conveniently point you to some solutions if you want to start or continue your online presence.
Domain Registrations, Renewals and Transfers
I use Domain Cost Club for domain registrations, renewals and transfers. I been using them now since November 2014. I find that they are reliable, do the job and are very cost effective.
If you are technical and already have practical cPanel Hosting expertise, you might find the cPanel Hosting solution I currently use hits the sweet spot for you. They are very cost effective. However in my opinion, you do need practical cPanel Hosting knowledge and experience. Their website support is during normal business hours.