Error while restoring a content backup


#21

Ok, I’m getting the same error when trying to upload to my server.


#22

Ok, we figured out the issue, the AJAX POST request times out after 20 sec even if you’re still uploading.
Basically, the way we upload the archive is not ideal for large files and we’re probably gonna have to rework that.

But it’ll take a bit to fix, so in the meantime, here is a workaround you can use if you’re comfortable with it:

  • Go to the content settings page
  • Open the Chrome dev tools (Right click the page and select “Inspect”)
  • Go to the “Sources” tab
  • Navigate to the following file: /content/js/content.js from the left pane
  • At line 59, you should see the following code:
        $.ajax({
          url: '/content/upload',
          type: 'POST',
          cache: false,
          processData: false,
          contentType: false,
          data: fileFormData
  • Add the following code between line 61 and 62:
          timeout: 300000,
  • You should now have:
        $.ajax({
          url: '/content/upload',
          type: 'POST',
          timeout: 300000,
          cache: false,
          processData: false,
          contentType: false,
          data: fileFormData
  • Save the change with Ctrl + S
    • The little star next to the file name at the top should disappear when you do that
  • Do NOT refresh the page
  • Upload the content archive

This will give you a timeout of 300s instead of 20s which should be plenty to upload that file.
The file gets reset every time you load the page, so you’d have to do that every time you want to upload content.


#23

Great news, I’m so glad you found out!

Unfortunately the quick solution didn’t work here, but I stopped the time, and in fact the failure is after 20 seconds (even with the new timout code).

Thank you anyway, and I can wait until the problem with the uploader is fixed.


#24

I forgot a step, I edited the previous post.
You need to save the change with Ctrl + S.
That’ll take away the little star next to the filename we can see at the top of your screenshot that means there are unsaved changes.


#25

Works! So happy here :slight_smile: thank you @c


#26

Happy to help.

74 is already cut and we’re not gonna have the time to get to a proper fix for 75, so we’re gonna increase the timeout in the mean time (in 75).
That should mitigate most of those problems.


#27

I alerted for this problem many months ago. It seems to me a bit strange that Boone noticed this problem before… Surely not many people did di backup and restore with their domains… Strange Indeed… PS… My backup is around 1gb will I be safe with this fix ?
:slight_smile: