Importing .Zip into Heartcore stalls and does not complete

[Bakersbakebread]

I have managed to successfully export from a local instance into a .zip file, the file size is 1.1GB (as it contains media).

The intention is to import this export inside of a Heartcore instance, originally the first instance was on an invalid version causing us to create a new one so we get the latest version of Deploy.

After getting access to the new project (and thus the new version of Deploy) I am able to trigger an import, however, when triggering with the zip that was aforementioned exported - the prompt freezes and does not continue.

I can see in the network tab that the file upload has started (but timing shows it has stalled).

I saw a previous issue: #214 but unfortunately as this is a Heartcore solution I am unable to create a composer, nor am I able to upload media directly.

Is there some mitigation my end that can be done to ensure this import succeeds? Do I need to be more patient, or is it destined to fail?

[AndyButland]

My guess is that you are hitting the limit described here for the size of upload.

If this is for an import into Heartcore where you won't be able to change these settings, I'd suggest reaching out to support to see if there's some other way they can help you get the media into the platform. Perhaps you can get the blob storage connection and use Azure Storage Explorer or some similar tool to upload the media files. Then, if they are in the expected place on the file system, if you just upload an export without the media in it - which will be much smaller - the media references in Umbraco should link up with the physical files.

[ronaldbarendse]

Umbraco Cloud does indeed have a maximum upload size of 500MB due to Cloudflare being in front of it, but I'm not sure what exact configuration Heartcore uses (it doesn't seem to configure the Umbraco:CMS:Runtime:MaxRequestLength setting, as the UI would otherwise already prevent you from trying to upload a bigger file)...

I would suggest manually splitting the ZIP archive if you want to do this yourself:

• Create a copy/backup of the original (especially if you can't easily recreate it by exporting again);
• Open the ZIP, remove the media-file folder and import this file (which should definitely be smaller than 500MB, as it will then only contain the UDA files). You should now have imported all schema and content, except the actual media files (the media items will exist, just not the files);
• Open the original ZIP again, but now remove everything except the media-file folder and the UDA files starting with media__ and media-file__:
  • Create copies of this edited ZIP archive and selectively remove files from the media-file folder (but keep all media UDA files), so you end up with multiple files that are less than 500MB;
  • Try to import these files (you might need to split this into even smaller ZIP archives if you still have issues uploading large files);
  • When these files are imported, all media items will be re-saved (but since media items aren't versioned, this doesn't really matter, as it will overwrite all existing media properties with the same values each import), but more importantly, the media files that are in the file are imported and the ones that aren't are silently skipped...