This release is a pre-release and may not be stable for production use.
Introduction
Allow to view content of archive files into plone.
How it works
Add a File with zipped content, this will be marked with ‘collective.archiveviewer.interfaces.IArchiveFile’.
Now you can access the content trough web by appending ‘@@contents/$filename’ to the path of your file.
For instance, if you have a file ‘foo.html’ inside the archive you can view it by going to ‘http://yourplone.com/yourzipfile/@@contents/foo.html’.
Supported archives
zip (application/zip)
NOTE: archives are supported trough adapters. You can simply register a named adapter providing ‘IArchiveReader’ interface and name it as the meta type to be supported (like ‘application/zip’).
Please, refer to ‘interfaces.py’ and ‘adapters.py’ for understanding how to write yours.
Issues
Please, submit any issue to https://github.com/collective/collective.archiveviewer/issues
Compatibility
Tested on Plone 3.3.6
Credits
Developed with the support of International Traning Center of the ILO.
This product was developed by Domsense in collaboration with Silvio Tomatis.
Release files for collective.archiveviewer 1.0b2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| collective.archiveviewer-1.0b2.zip | 24.0 kB | Without provenance | Details for collective.archiveviewer-1.0b2.zip |
Release files / collective.archiveviewer-1.0b2.zip
| Download URL | collective.archiveviewer-1.0b2.zip |
|---|---|
| Size | 24.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a14c86104447bbc7a5df00fb1e7aaa76cf7c2017a87f62318e7d7115371205ff
|
|
BLAKE2b-256 checksum How to use checksums |
84fcdfc2387ff1f717e41417a003e84fcd12cc9821b13a4d9adc7e08aa73edb8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.archiveviewer 1.0b2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
