S3-Uploads
S3-Uploads copied to clipboard
Strange issue with 2.2.2 version and .zip files
I'm using the 2.2.2 version and WordPress Version 5.6
I noticed something strange when I uploading a plugin or theme .zip file just from the WordPress interface
// using interface If S3-Uploads activated and I upload a new plugin or theme zip file The file loses approximately half of its size, files are missing and the plugin won't able to work, and if I deactivate the S3-uploads plugin everything works well.
// using FTP when I upload my plugin using FTP and unzip it via command and enable the plugin using CLI, nothing strange happened
So the problem just when uploading a .zip file from WordPress Interface
By the way, I disabled all plugins I have and kept S3 Uploads and the problem still exists.
Did anyone face this before?
@NurdinDev I think this is because you might have downloaded the source code ZIP file, which doesn't include dependencies. It looks like our auto-bundling of deps hasn't worked for 2.2.2 (see https://github.com/humanmade/S3-Uploads/releases). If you download manual-install.zip
of 2.2.1 and see if that works.
We're also facing a similar issue in that when we upload a theme or plugin update, some files that are unzipped are completely empty (0KB). Disabling the plugin allows us to upload the theme or plugin without issues.
We're using the manual-install of 2.2.1 and then overwriting with the source code of 2.2.2 since there is no manual-install of 2.2.2.
Can confirm the same issue, uploading a plugin/theme .zip via the Wordpress UI will sometimes result in the some of the extracted files having a filesize of 0 bytes.
Does not occur when s3-uploads is disabled.
I have installed 2.3.0 and the version reads Version 2.2.2
After a customer reported an error with our S3 Image Optimizer plugin and S3 Uploads, I discovered the same thing. If S3 Uploads is active when we install S3 Image Optimizer, our aws-autoloader.php file is empty and that breaks everything, as one would expect. I updated my site to version 2.3 (that still reports being 2.2.2), using the manual-install.zip and it does not work. I also tried manual-install.zip from the 2.1 release, and the bug remains.
This is still an issue. Nearly every time we install a plugin via zip upload it ends up corrupted. We've resorted to simply unzipping the file manually and placing the plugin into the repository by hand.