Hello!

I'm attempting to install beta-7 however both of the available archives, manual, quick, will not unpack but instead result in the pictured error. Anyone else with the same issue?

package-archives.webp

(Click to enlarge)

Aside: webp format not supported for images?

Thanx!
SD

Hello,

I cannot reproduce this issue on Windows 11; it downloads and extracts just fine for me. The byte number provided is one byte shy of the actual size, so perhaps it's a corrupt download. Try downloading it again and see if you get the same issue.

If you do, what operating system are you using? What utility or browser are you using to download the file? Also what utility are you using to extract the ZIP file?
 

---

I checked into WEBP. Support for that was implemented in https://composr.app/tracker/view.php?id=4049 . But apparently it wasn't listed by default as an allowed image file. So I'll fix that for the future.

I'm testing by adding a WEBP AI-generated image. Not sure yet if attachments will actually render it.

Whisk_c104496915.webp

(Click to enlarge)

Edit 2: it does not. I found a comment by Chris. WEBP is not rendered in attachments because it's not web-safe. I disagree. There is a PHP function that allows us to work with WEBP images. I will add to the tracker and put you as the author so you get credit.

Hi Patrick!

You nailed it: "The byte number provided is one byte shy of the actual size".

I'm installing on the following:


Error:

Fix:

Result:

composr_manualextraction_installer-11.beta7.MOD.zip is increased by 1 byte.

New file extracts without error.

Thanx kindly!

Glad it worked!

Please do me a favour and re-download the manual installer again using the same method you did before, and let me know if it comes up one byte short again. I want to see if this was a one-off fluke (network issue perhaps) or a legit bug. Thanks!

Lol, the plot thickens! :-) It appears to be limited to the Thorium browser (thorium.rocks) I'm using which is a customized instance of Chromium. Brave and LibreWolf do not have the issue nor does "wget" or "curl"; all download to the correct byte count.


Apologies, I should have checked this first!

It's been a while so I'm a bit out of practice as far as best testing goes :-)

That's very strange. Thanks for the insight!