• Resolved tremlas

    (@tremlas)


    Having recently upgraded the plugin from 3.1.5 (I think) to 3.1.6.2 I was surprised when the generated zip file had corrupted versions of the large files on my site. The corruption was that the files had been truncated to 20M (instead of the files actual size of about 100M). Luckily as I use diff tools to find out what actually needs to be updated on the uploaded static version of the site I was able to discover the corruption during that upload process (and the was able to use the change log of simply static to discover how to increase that 20M limit to 200M and regenerate the zip file (and I want to thank you for having a useful change log!). However it would have been nice if Simply Static had been able to warn me in some way that the files had been truncated (for example, with a fake HTTP code)

Viewing 1 replies (of 1 total)
  • Plugin Author patrickposner

    (@patrickposner)

    Hey @tremlas,

    good point!

    I’ll add that to our GitHub repository, and we can have a look!

    I’m sure we can figure out how to make the experience a bit smoother (either by adding it to the debug log or showing a warning in the activity log).

    I like the idea of a fake HTTP code – this would allow us to add a little flag in the export table, so you know exactly which file was corrupted!

Viewing 1 replies (of 1 total)
  • The topic ‘suggestion: error/warning when a large file is truncated’ is closed to new replies.