Ticket #13680 (new Bug)
Old Products in the Downloads section contain empty archives
Reported by: | do3cc | Owned by: | plone-website@… |
---|---|---|---|
Priority: | minor | Milestone: | 4.x |
Component: | Website | Version: | |
Keywords: | Website | Cc: |
Description (last modified by do3cc) (diff)
Interestingly the old Plone release do not have the issue.
This is the oldest package with empty archives:
http://plone.org/products/listingpages/releases/1.0b3
I stopped searching at releases from 2012:
http://plone.org/products/collective.js.twittertext/releases/1.0
The file is still there, but empty.
Since I got asked, what the problem is: I expected to be able to download packages of code from the download section of plone. What I found were download links that pointed to empty files. I did not find the code, only empty files.
Change History
comment:1 Changed 3 years ago by do3cc
- Owner set to plone-website@…
- Component changed from Unknown to Website
- Description modified (diff)
comment:3 Changed 3 years ago by aclark
Perhaps this issue began with the recent declaration of config bankruptcy on plone.org. If you have time, please look for the appropriate rewrites here:
Then add them to:
and send a pull request. That *should* fix the problem AFAICT, unless I totally misunderstand what the issue you are describing is.
comment:4 Changed 3 years ago by do3cc
Ok, I understood the old configuration. It did redirects into the dist.plone.org/packages. Somehow, binary files have been copied from the zope database into the file system. I assume, that in the same process, the files in the zope db have been replaced with an empty file. This makes sense in the context of a plone 3 site, where we had no blobs and delivering large files from the filestorage was inefficient. Now, new release are actually in the zope database and their contents aren't emptied any longer. I suspect that this also means, that the files aren't automatically copied to dist.plone.org any longer. If this is the case, adding the redirects might be a bad idea. Maybe what is needed is a migration, where the files are in dist.plone.org are reuploaded into plone. They would end up as blobs then.