#8 — Plone 3.3.4 calendar portlet breaks following activation of Calendaring 0.4.0 (and Marshall 1.2.1)

by Graham Perrin last modified Jan 17, 2011 03:39 PM
State Unconfirmed
Version: 0.4
Area Functionality
Issue type Bug
Severity Important
Submitted by Graham Perrin
Submitted on Feb 06, 2010
Responsible
Target release:
Following activation of Calendaring 0.4.0 (and Marshall 1.2.1) it's not possible to browse back or forward in the calendar portlet of Plone.

(You might reach the extents that you reached prior to activation of Calendaring 0.4.0, but you can't browse beyond those extents.)

Tracebacks and debug information to follow.
Steps to reproduce:
 1. ZMI, root

 2. add a Plone site

 3. view the site

 4. in the calendar portlet: browse back a little, forward a little

 5. activate Calendaring 0.4.0
Added by Graham Perrin on Feb 06, 2010 03:30 PM
Plone 3.3.4
CMF 2.1.2
Zope (unreleased version, python 2.4.6, darwin)
Python 2.4.6 (#1, Oct 12 2009, 14:01:27) [GCC 4.0.1 (Apple Inc. build 5493)]
PIL 1.1.6

(It's Zope 2.10.11 without a version.txt file, but that's not relevant to this bug; it bites on sites where the Zope version issue is worked around.)
Attached:
8-debug-information.html — text/html, 47 Kb
Added by Graham Perrin on Feb 06, 2010 03:32 PM
A Terminal window view of client1 running in foreground, from the point at which I opted (in ZMI) to activate Calendaring.
Attached:
8-001.txt — text/plain, 32 Kb
Added by Graham Perrin on Feb 06, 2010 03:58 PM
Stop client1,
stop zeoserver,
start zeoserver
the calendar portlet is more broken than was obvious at first;

> Error

> There was an error while rendering the portlet.

Uninstalling Marshall does not seem to improve the situation.

Uninstalling Calendaring does not seem to improve the situation.

Stop client1,
stop zeoserver,
start zeoserver … 
Added by Graham Perrin on Feb 06, 2010 04:41 PM
HIghlight from the traceback:

TypeError: catalog_getevents() got an unexpected keyword argument 'path'

Discussion: <http://n2.nabble.com/-tp4507875p4525910.html>
Added by Guilherme Torres Castro on Jan 17, 2011 03:39 PM
I fix it , downgrading plone.app.portlet from 1.2 to 1.1, just change the version in version.cfg, run buildout and restart Plone.

No responses can be added.