Hi Magnolians We're having some trouble setting document.domain by Javascript.
This breaks the GWT components in Magnolia author. I think it is the one loaded by "/.resources/editor/info.magnolia.templating.editor.PageEditor/info.magnolia.templating.editor.PageEditor.nocache.js". We had the same problem already in different projects when including third-party GWT apps. The hack we used then, was to modify the GWT generated .cache files and add the document domain manually. There is also an option to link the GWT components differently at compile time (which should solve the problem as well): http://code.google.com/p/google-web-toolkit/issues/detail?id=5746 Has anyone ever dealt with this problem? Again, I'm thinking of modifying the cache files. Maybe even on the fly by some filter. But maybe there is another, nicer, way? Any help is appreciated Cheers Andy -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=23d255fe-1df7-43bd-bf61-dbf3e5da60fe You are invited to Magnolia Conference. Less than a month to go! Register now: http://www.magnolia-cms.com/conference/register.html ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
