Hello
The workaround for this problem as mentioned in
http://jira.magnolia-cms.com/browse/MAGNOLIA-2782 doesn't work for me.
Trying to set the current Page via
MgnlContext.getAggregationState().setMainContent(
MgnlContext.getAggregationState().getMainContent().getAncestor(level)
);
does not influence the result of
MgnlContext.getWebContext().getAggregationState().getHandle();
which is currently used in the editButton Tag.
My ugly workaround for this ugly situation is:
<c:set var="orig"><cms:editButton label="Edit Header" dialog="header"
contentNodeName="headerPar"/></c:set>
<c:set var="newValue">${cmsfn:currentPage().handle}</c:set>
<c:set var="oldValue">${cmsfn:mainPage().handle}</c:set>
${fn:replace(orig,oldValue,newValue )}
HTH
Tobias
2009/6/11 Christian Menzel <[email protected]>:
>
> Hello!
>
> I just tried to port an existing 3.6.5 installation to 4.1RC5 and
> noticed a strange behavior.
> We use <cms:loadPage/><cms:editButton/><cms:unloadPage/> constructs to
> edit global values in our pages.
> This works in 3.6.5, but in 4.1RC5 the edit dialog is called with the
> path of the MainContent instead of the path of the CurrentContent or
> ActivePage (in old speak) in the 'mgnlPath' parameter.
>
> Is this a bug or intended?
>
> Regards
> Chris
>
>
> ----------------------------------------------------------------
> 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]>
----------------------------------------------------------------
