Removing the 512MB upload size limit on All-in-One WP Migration Plugin

A WordPress development workflow can be difficult to optimize, especially when working in a team environment. You wont have trouble finding a few well written articles online concerning version control setups and project structures. Setting up a new project is smooth when you’re using a Git repository of some flavor for your theme content, and Database Sync or a similar plugin to sync your local and live databases.

What about the case in which you inherit an existing WordPress site?

It’s not uncommon to need to pull all of a site’s plugins, settings, and media content to a local development environment at least initially. This is typically part of our “on boarding” process at work.

Simply syncing themes and databases as you typically would in your development workflow is not enough in this instance. With a plugin known as All-in-One WP Migration, you’re able to export an entire WordPress instance to a single file with an extension .wpress. You’re then able to turn right back around and import that file to another WordPress installation to create a clone.

Here is what the steps look like to export a production site to a file.


At this point, depending upon the size of the backed up file, a blank installation of WordPress may be all that’s necessary to clone the production site.

wpmigration4-1024x733

If the size of your .wpress file exceeds 512MB, you will be prompted to purchase the Unlimited Extension of All-in-One WP Migration.  If you’re inheriting a site that’s been in production for a while, it’s likely that the backup file is over this small size limit (see a fix for this below).

 

Hacking the plugin seemed like a reasonable thing to try before making the $59 dollar purchase of the Unlimited Extension (which comes with lifetime updates, and unlimited support).

Go ahead and open up

/wp-content/plugins/all-in-one-wp-migration/constants.php

Lines 199:201 define the file upload size limit, there’s a nice comment there indicating such. If you’d like to control+f  “size”, it should take you right to it.

// =================
// = Max File Size =
// =================
define( 'AI1WM_MAX_FILE_SIZE', 536870912 );

You’ll see the max size is defined in Bytes. In order to increase the upload size limit to 4GB, simply multiply the number seen here by 8.

// =================
// = Max File Size =
// =================
define( 'AI1WM_MAX_FILE_SIZE', 4294967296 );

We’ve been getting lazier and doing this, which works the same as above.

// =================
// = Max File Size =
// =================
define( 'AI1WM_MAX_FILE_SIZE', 536870912 * 8 );

Save the file and navigate back to the “import” function for the All-In-One Migration Plugin. The file upload limit now reads 4GB.

The plugin will no longer reject your large file uploads.

You are all set! Feel free to comment below if you have any questions

17 responses on "Removing the 512MB upload size limit on All-in-One WP Migration Plugin"

  1. I Change it on my Server but its still Stock @512 MB

  2. Are you test it local server or your host server.

  3. HI . I have change the limit. But when i upload the file, the upload stuck by 1.56%. Do you know what the problem is?

    THanks!!

  4. Hi, I am trying to restore a client site that crashed yesterday and I am getting a message. “Activiating mu-plugins…” and the plugin is stuck.

    But it seems some of the site has restored see here:
    http://mariabrito.com/wordpress/contact/

    Any ideas whats going on, I could really appreciate your help. If I can’t get it to go, I’ll have to pay the client’s host $150 to restore an 7-14 day old database that would loose all the work I have done lately.

  5. Thank you for the hack!! You just saved me $69 that I never considered negotiating into my client contract.

    Cheers!!

  6. Hi Joseph

    You saved my life. Or it feels like it. This is by far the simplest best solution.
    Thx a lot

  7. Thanks a bunch! That was so easy.

Leave a Message

Your email address will not be published. Required fields are marked *