Overview

System to enrich a file content type in Plone with a marker interface regarding its mimetype.

Description

Please note that atreal.richfile.qualifier is a Plone component for developers. Do not expect anything more in your Plone site if you don’t use Plone components that may use atreal.richfile.qualifier, such as:

atreal.richfile.qualifier works on Plone 3 with ATFile and on Plone 4 with ATFile and ATBlob. You can easily configure your own file content type:

<five:implements
    class="Products.ATContentTypes.content.file.ATFile"
    interface=".interfaces.IFileQualifiable"
    />

Control Panel

Few options are avalaible in the Control Panel :

‘Update all contents’: will update all contents of the portal supported by this plugin.
‘Clean all datas’: will clean datas created by this plugin, for each supported content of the portal.

Important: These operations will take a while, and may slow down the site significantly while the content is updated.

Important: These operations search by the interface provided by the content in portal_catalog, so if you already have contents in your site when you install this package, you have to update ‘object_provides’ index first.

Important Notes

The version 1.1.1 of atreal.richfile.qualifier is not Plone 3 compatible ! Please use version 1.1.2 instead.

Authors

atReal Team
- Thierry Benita [tbenita]
- Matthias Broquet [tiazma]
- Florent Michon [f10w]

Contributors

atReal Team
- Romain BEYLERIAN [rbeylerian]

Credits

Sponsorised by City of Albi (France), http://www.mairie-albi.fr/

Changelog

1.1.2 (2012-04-10)

Plone 3 Compatibility : Restore Plone 3 compatibility broken in version 1.1.1 ! [rbeylerian]
Misc : Fix typo in HISTORY.txt [rbeylerian]
Misc : Replace tabs with whitespaces in configure.zcml [rbeylerian]

1.1.1 (2011-11-15)

Plone 4 Compatibility : Update CMF core permissions declaration in ZCML [rbeylerian]
Plone 4 Compatibility : Avoid five:implements deprecation warning under Plone 4 [rbeylerian]

1.1.0 (2011-04-27)

Plone 4 Compatibility : minors CSS adjustments [f10w]
Plone 4 Compatibility : add control panel action icon with the new way [f10w]
Plone 4 Compatibility : update control panel template [f10w]
Plone 4 Compatibility : replace bobo traverse method on the view by an adapter which is the right way even on Plone 3 [f10w]
Plone 4 Compatibility : file content type by default in Plone 4 is ATBlob [f10w]
Cleanup package-structure [f10w]

1.0.0 - Unreleased

1.0.0rc1 - 2009-12-23

First release candidate [f10w]

1.0.0beta3 - 2009-09-11

Add a patch to kss.core [f10w]

1.0.0beta2 - 2009-09-08

Delete a call to an external package useless not required [f10w]

1.0.0beta1 - 2009-09-04

First public release [tbenita, tiazma, f10w]

Metadata

Release files for atreal.richfile.qualifier 1.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for atreal.richfile.qualifier 1.1.2
File	Size	Uploaded	Provenance
atreal.richfile.qualifier-1.1.2.zip	45.2 kB	Apr 10, 2012	Without provenance	Details

Release files / atreal.richfile.qualifier-1.1.2.zip

Download URL	atreal.richfile.qualifier-1.1.2.zip
Size	45.2 kB
Tags	Source
SHA-256 checksum How to use checksums	`270a0d36373e75bc205c53f57131a7a5c05b5212e61263413ca8b490d6763147`
BLAKE2b-256 checksum How to use checksums	`eb4b6be9f288243aab39de4abb614fef8ce2f82d6be0eb2ba46f85f9983dd165`
Upload date	Apr 10, 2012
Uploaded using Trusted Publishing? What is trusted publishing?	No

Security for atreal.richfile.qualifier 1.1.2

Report project as malware

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.