This release is a pre-release and may not be stable for production use.
Introduction
Provides an archetypes validator for file and image fields to only allow specific content types to be added.
Example
from Products.ContentTypeValidator.validator import ContentTypeValidator
...
FileField('file',
validators = (ContentTypeValidator(('audio/mpeg', 'audio/x-mp3', 'audio/x-mpeg', 'audio/mp3',))),
widget = atapi.FileWidget(
description = '',
label=_(u'label_audio', default=u'Audio file'),
show_content_type = False,),
),
...
History
2.0b4 (2012-11-20)
Added unittests [gbastien]
Updated translations [gbastien]
2.0b3 (2010-10-24)
Updated German and Français translation [macagua]
Added Spanish translation [macagua]
Added master template .pot file [macagua]
Set zip_safe flag to False
2.0b2 - (2010-10-21)
Removed unused generic setup profile
Added README
2.0b1 - (2010-10-20)
First public release
1.2 - (Unreleased)
Fixed mimetype parsing in validator
1.1 - (Unreleased)
Changes added / profiles added / version increase
1.0 - (Unreleased)
Init Rls for plone3
Metadata
Release files for Products.ContentTypeValidator 2.0b4
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 |
|---|---|---|---|---|
| Products.ContentTypeValidator-2.0b4.zip | 21.4 kB | Without provenance | Details for Products.ContentTypeValidator-2.0b4.zip |
Release files / Products.ContentTypeValidator-2.0b4.zip
| Download URL | Products.ContentTypeValidator-2.0b4.zip |
|---|---|
| Size | 21.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
39712ee499b8c8b859a28457c925c73dc5b0b71d2c259618741985535066f37c
|
|
BLAKE2b-256 checksum How to use checksums |
7873d532b7a54edfe02eb56d2cb312ba3405268df75ab616b01252d2c2801ab9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.ContentTypeValidator 2.0b4
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.