Please login or register to participate.
gogobd May 26, 2010 02:20 PM
I just tested an upgrade from 3.1.1 to 3.1.3 - we want to upgrade our production servers soon. There are two issues at the moment. One issue is that i had to add

zcml -=
zcml +=

to our custom buildout configuration file - otherwise the instance would not start. The second issue is a runtime issue: i see that sometimes generates an img tag that reads:

<img src="%useravatarurl" class="commentavatarimg" />

and that should usually be sesolved to a *real* avatar-url but is not. These requests also take a long tme and a lot of CPU since they can not be resolved and errors take long to render in plone. Where can i file these two bugreports? The rest of the upgrade seems to have gone perfectly well! Thank you. Gogo.
Replies (3)
gogobd May 26, 2010 02:23 PM
Ah, and btw the template where it comes from is this one i suppose:[…]/
dhiraj May 26, 2010 02:42 PM
The caching.zcml was added as a replacement for the archetypes.schematuning package since it is included in schemaextender. It is safely disable-able exactly the way that you have; there are no side-effects (apart from the potential reduction in content creation performance). What was the buildout / start error that you were getting?
Potential fix for this is to run the buildout once in -n mode to get all new packages.

The %useravatarurl problem that you are reporting: Is it from the browser itself? That is, are you getting a broken image in view on the page, or are you, like me, seeing this happen on the Activity Stream view on the Network log in Firebug net tab? ;)
The file is used as a template placeholder formatting for the comments that will newly be created by AJAX as new / reply comments in the Activity Stream view. The placeholder tokens are replaced in browser, at runtime, using jQuery.

I noticed this 404 on the firebug net tab myself, while researching/debugging migration to newer jQuery versions, but I'm not sure if it was caused because of the presence of firebug itself (during it's evaluation of the display:none'd html), or if the browser itself was actually trying to load the src token as an actual image.

As always, please submit all new issues directly to the Cynapse ODN tracker, that is the best way.
Current issues targeted for next release:
New issues: