• Resolved johnwp413

    (@johnwp413)


    In 5 months I’ve made 5 duplicates of a live site for tweaking it locally/offline. The first 4 archives ranged from about 50 MB to 62 MB as the site progressed. The largest of the 4 was the most recent one, about 2 weeks ago. Today I wanted a new archive to work with because some very minor changes were made online including updates to the most recent WordPress version and a theme update. One more page was added to the website in that 2 weeks, but it isn’t a big load (one small image, not a lot of text).

    Today I am creating the 5th archive following exactly the previous steps. For the first time I get warnings/notices during scan advising a size problem (over 250 MB uncompressed) and a unicode symbol problem. I excluded or filtered three files listed and continued to archive as a test. The resulting archive is a problem and it is nearly 140 MB in size (compressed).

    The created zip file is not valid for any win-zip or 7-zip, etc. tool I’ve tried after getting the error message when running the installer script on my local machine.

    I don’t know where to begin to figure out why in just a short period of time and with minor changes to the website I went from an easy routine with a 62 MB archive to a problem archive over double the size. Could the WordPress update have been that big of a load?
    Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hey John,

    It’s tough to tell here a few things you might look for:

    1. A sym-link was added (sometimes hosts add them for various reasons)
    2. If you have another backup plugin that ran and created a large backup file.
    3. Any other scheduled routine that might add data…

    If you want to be pin-point exactly what changed then goto the wp-snapshots directory open the .json files for the packages you built and goto https://www.diffchecker.com/ and you can see how the packages differ that way you can be 100% sure.

    Thread Starter johnwp413

    (@johnwp413)

    Thanks for the speedy reply.

    It worked after I did the following:

    • omitted the addon domain (which has always been there), which means I filtered the directory /home/originaldomain/public_html/addondomain.com (found out my client had added 2 big posts/pages to the other domain)
    • ran the archive scan again and only got warning for unicode symbols (again) and not for size
    • out of curiosity checked this newest archive with 7-zip and it was able to access
    • ran the installer script on my local machine and it worked this time

    For what it’s worth the offending characters appear to somehow be a part of a plugin called Simple Cache. It was only used as a quick fix for something, so I may revert the site to perhaps a more advanced method to improve loading/caching. Although I selected the offending files before and rescanned, for some reason it didn’t work.

    Is there any other cache that is either recommended or advised against for compatibility? I will probably advance the site to something like WP Super Cache or W3 Total Cache. It will just require a little more education for the users/client.

    There really are not any recommendations for or against any. It is just recommended to always clear the cache before building…

    Hope that helps~

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Errors extracting zip file (new problem)’ is closed to new replies.