Hi Grégory

Yep it coughed up the following:

magnolia 3.0.2:
Error: uncaught exception: [Exception... "Access to restricted URI denied" code: "1012" nsresult: "0x805303f4 (NS_ERROR_DOM_BAD_URI)" location: "http://landweg.ch/author/.magnolia/pages/javascript.js Line: 1161"]

and for magnolia 2.1.5:
Error: uncaught exception: [Exception... "Access to restricted URI denied" code: "1012" nsresult: "0x805303f4 (NS_ERROR_DOM_BAD_URI)" location: "http://ruckstuhl.com/author/admintemplates/js/ admincentral.jsp Line: 1175"]

Cheers, Thomas


On 08.06.2007, at 00:24, Grégory Joseph wrote:

Hi Thomas,

Did you notice if that triggered some kind of javascript error ? If so, that might help fixing a potential on either Magnolia's or that extension's side.

g

On Jun 7, 2007, at 23:36 , Thomas Martin wrote:

Hi Magnolians

Just bumped into a rather tiring situation: a Firefox extension that I must have updated without noticing kept Firefox 2 from rendering any tree in the admin central.

Since I was not aware of the update I guess you can imagine I spent some bad time from panic to frustration until I found out that it all came down to a little Add-on. The bugger is called SearchStatus (http://www.quirk.biz/ searchstatus/ - 2007-05-23: ver 1.20)

It rendered my FF 2.0.0.4 on 10.4 in tree swallowing monster: no tree (website/config/whatever) showed up any more in any version of magnolia (2.1.5 - 3.0.2)

Just thought I let you know.

Cheers, Thomas

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------

Reply via email to