Calendar product for the Zope Content Management Framework
- Products.CMFCalendar Changelog
- 2.2.3 (2014-02-19)
- 2.2.2 (2010-10-31)
- 2.2.1 (2010-07-04)
- 2.2.0 (2010-01-04)
- 2.2.0-beta (2009-12-06)
- 2.2.0-alpha (2009-11-13)
- 2.1.2 (2008-09-13)
- 2.1.2-beta (2008-08-26)
- 2.1.1 (2008-01-06)
- 2.1.0 (2007-08-08)
- 2.1.0-beta2 (2007-07-12)
- 2.1.0-beta (2007-03-09)
- 2.1.0-alpha2 (2006-11-23)
- 2.1.0-alpha (2006-10-09)
- Earlier releases
The CMFCalendar product is an example of creating a CMF Product. The CMFCalendar product is also expected to be a generally useful out of the box and skinnable to accomodate customization within your existing CMF instance. To see how to go about building a CMF product, this hopefully allows a developer to follow through the process of registering their product, skins, and help with the CMF by example. It shows how an object is created and registered with the types_tool, necessary skins added to the skins_tool, with the Calendar skins directory added to the skin paths, and providing portal_metadatool with an Element policy for the content_type of the object.
For installing set the active site configuration of your site’s setup tool to the CMFCalendar profile and import all steps.
After installing the CMFCalendar you should notice a calendar appear in your CMF. This is fully customisable to your portals needs.
- Declared dependency on zope.app.form.
- Fixed tests to be compatibility with DateTime 3.
- Adjusted test layer setup to work with Zope 2.13.0a2.
- Fixed Chameleon incompatibilities in some templates.
- Fixed ViewPageTemplateFile import to use the correct version from Five.
- Deal with deprecation warnings for Zope 2.13.
- no changes from version 2.2.0-beta
- no changes from version 2.2.0-alpha
Got rid of redundant icon related type info properties. (https://bugs.launchpad.net/zope-cmf/+bug/397795)
moved the Zope dependency to version 2.12.0b3dev
Cleaned up / normalized imports:
o Don’t import from Globals; instead, use real locations.
- o Make other imports use the actual source module, rather than an
intermediate (e.g., prefer importing ‘ClassSecurityInfo’ from ‘AccessControl.SecurityInfo’ rather than from ‘AccessControl’).
o Avoid relative imports, which will break in later versions of Python.
profiles: Added an add view expression to the Event content type definition.
Fixed a bug were the last day of each month was missed. (see https://dev.plone.org/plone/ticket/7238)
Event GenericSetup type definition: Add an icon URL expression to the Event content type definition.
Event: Added basic iCal and vCal views (https://bugs.launchpad.net/zope-cmf/+bug/161714)
ZMI: Prevent users from creating content through the ZMI by hiding the entry for “CMFCalendar Content”.
Event: ‘addEvent’ no longer sends add events.
profiles: Removed obsolete local import step registrations.
setup handler: Improved ‘various-calendar’ import step. Added flag file check and global registration.
CalendarTool: Added a new method getNextEvent to grab the next event relative to a given point in time. (http://www.zope.org/Collectors/CMF/462)
- no changes from 2.1.2-beta
- completed devolution from monolithic CMF package into its component products that are distributed as eggs from PyPI.
- no changes
- Testing: Derive test layers from ZopeLite layer if available.
- 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.
- 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)
- Fixed DST-driven test breakage by adding an optional ‘zone’ argument to the DublineCore methods which return string renditions of date metadata. (http://www.zope.org/Collectors/CMF/476)
- 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
- Zope3 style browser views are now used by default. An additional setup profile allows you to hook up the oldstyle skins and to make customizations TTW.
- 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.
- 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.
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