On 3/26/12 7:48 AM, Jean-Michel FRANCOIS wrote:
> Hi,
>
> I already have discuss this topic last year, but I still have the issue.
>
> I have reported the bug at
https://dev.plone.org/ticket/12800>
> Using getUtility(ITinyMCE) force you to not trying to output value
> like URL, because request is not bind on context, so absolute_url
> calls will never output a URL but a PATH.
>
> The code start from a browserview, but use getUtility to compute the
> TinyMCE configuration, so URL of @@tinymce-getstyle will never be a
> valid URL.
>
> So the question is: Why you don't want to use getToolByName, so the
> request is bind on the context ? Mean Change all calls
> in TinyMCEBrowserView if getUtility by getToolByName.
>
> An other solution that seems used in the same view will give
> portal_url as a new arg of the method ITinyMCE.getConfiguration.
>
It looks like the utility lookup in five.localsitemanager is
intentionally removing the request container from the acquisition chain.
I'm not sure what the rationale is for that, but given that, +1 for
updating it to use getToolByName instead of getUtility.
David
----------
David Glick
Web Developer
[hidden email]
206.286.1235x32
GiveBIG is coming! Mark your calendar for May 2 and get ready to give big to Groundwire
on this community-wide day of giving.
http://www.seattlefoundation.org/npos/Pages/Groundwire.aspx------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Locked
