This project has been archived by its maintainers, and is no longer receiving any updates.
Products.CMFTopic
This product declares a topic content type for the Zope Content Management Framework (CMF).
Products.CMFTopic Changelog
2.1.2-beta (2008-08-26)
completed devolution from monolithic CMF package into its component products that are distributed as eggs from PyPI.
2.1.1 (2008-01-06)
no changes
2.1.1-beta(2007-12/29)
Testing: Derive test layers from ZopeLite layer if available.
2.1.0 (2007-08-08)
Fixed all componentregistry.xml files to use plain object paths and strip and slashes. GenericSetup does only support registering objects which are in the site root.
2.1.0-beta2 (2007-07-12)
moved the Zope dependency to version 2.10.4
Remove antique usage of marker attributes in favor of interfaces, leaving BBB behind for places potentially affecting third-party code. (http://www.zope.org/Collectors/CMF/440)
Add POST-only protections to security critical methods. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0240)
2.1.0-beta (2007-03-09)
moved the Zope dependency to verson 2.10.2
Tool lookup and registration is now done “the Zope 3 way” as utilities, see http://svn.zope.org/CMF/branches/2.1/docs/ToolsAreUtilities.stx?view=auto
2.1.0-alpha2 (2006-11-23)
moved the Zope dependency to version 2.10.1
Fixed test breakage induced by use of Z3 pagetemplates in Zope 2.10+.
browser views: Added some zope.formlib based forms.
testing: Added test layers for setting up ZCML.
2.1.0-alpha (2006-10-09)
skins: Changed encoding of translated portal_status_messages. Now getBrowserCharset is used to play nice with Five forms. Customized setRedirect and getMainGlobals scripts have to be updated.
Profiles: All profiles are now registered by ZCML.
ZClasses: Removed unmaintained support for ZClasses. Marked the ‘initializeBases*’ methods as deprecated.
Content: Added IFactory utilities for all content classes. They are now used by default instead of the old constructor methods.
Content: All content classes are now registered by ZCML. ContentInit is still used to register oldstyle constructors.
setup handlers: Removed support for CMF 1.5 CMFSetup profiles.
Earlier releases
For a complete list of changes before version 2.1.0-alpha, see the HISTORY.txt file on the CMF-2.1 branch: http://svn.zope.org/CMF/branches/2.1/HISTORY.txt?view=auto
Download
Release files for Products.CMFTopic 2.1.2-beta
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.CMFTopic-2.1.2-beta.tar.gz | 29.1 kB | Without provenance | Details for Products.CMFTopic-2.1.2-beta.tar.gz |
Release files / Products.CMFTopic-2.1.2-beta.tar.gz
| Download URL | Products.CMFTopic-2.1.2-beta.tar.gz |
|---|---|
| Size | 29.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b5029057b1a53bd82bc2dfcadc67ba596e6bf24199a2d1c52d13da1fc7ba25c9
|
|
BLAKE2b-256 checksum How to use checksums |
d00796b475c87173baced3f818974076584e6cc7f43ca00fa570683494f31fba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.CMFTopic 2.1.2-beta
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.
