Issues known at release time
All issues found post-release are now logged in the issue tracker at: http://plone.org/products/ecampaigning-tool/issues. Please post issues there.
0.2 release candidate
- If you are running the tracking script as an access rule (checkIncoming.py), aggressive search engine bots or a very high volume action (1000+ within 20 minutes) could trigger a site-wide error (MaxTransientObjectsExceeded) if you use the default Zope configuration. The most common bots (Google, Yahoo and MSN) are now detected and no session set to prevent this problem, but it could occur with other bots and high volume actions. To reduce the risk of it occurring: a) add the bots that traverse your site to the ignore list in checkIncoming.py, b) increase the "Maximum number of subobjects" value for the transient object container at the root of your Zope instance (1000 is default), c) reduce the "Data object timeout value (in minutes)" value (20 is default).
- Support for Plone 2.1 has not been explicitly removed, but it is regardless likely the release is probably no longer working on Plone 2.1. Please let us know if you need to run the tool on Plone 2.1 (AND can not upgrade to a more recent version of Plone).
0.1.9 (OBSOLETE)
- If you make an Action Message editable, the Action Edition view will show raw HTML with no WYWSIWYG element, even for logged-in users. I would suggest that Action Message edits be plain-text only, and if default Action Message text is created as HTML, that it be converted to plain-text before being presented to the user for edits. (Hopefully this routes around the need to allow anonymous site visitors to use a WYSIWYG editor, which seems like a potential source of confusion, compatibility issues and Kupu-chaos.) --Jon Stahl
