Seams to be a tricky one. The stacktrace tells me that the aggregation state should be initialized (the aggregator filter was executed). Normally this exception occurs if one executes code in the system context.
Debugging hints: - verify that the created context (in the context filter) and the one used in FreemarkerTemplateRenderer.onRender() is the same -> should be - is the current context an instance of WebContext? - debug if the aggregation state is set (reset?) Philipp On 23.04.2010, at 14:52, Matteo Pelucco wrote: > > Hi all, > I have a problem. > > I'm going to migrate an existing working Magnolia-based environment from 4.1 > to 4.3.1. > > Everything since now has worked fine, the next task is to migrate the > websites developed with previous version to 4.3.1. > > We use a custom extension of STKParagraphRenderer and STKTemplateRenderer, > because in our .ftls we use a bunch of object related to platform. > > The problem is that when I switch from "stk" paragraph type to "ttk" (our > shortcut code) I receive the exception in subject. > > * It seems that the WebContext is lost: * > 2010-04-23 14:46:32,662 ERROR info.magnolia.cms.taglibs.Include: Can only get > the aggregation state within a WebContext. > java.lang.IllegalStateException: Can only get the aggregation state within a > WebContext. > > ------------------------------------------------ > Full stack trace: http://pastebin.com/s3SimG4h > My custom paragraph renderer: http://pastebin.com/XSghcMah > My custom template renderer: http://pastebin.com/fjephuzp > > > Any idea? > I'm going crazy about it... > > > Matteo > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
