We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 26964
    • 8 Posts
    ok, im not sure what ive changed but iv managed to totally break the ajax manager in FF, i just noticed i get a error in mootools


    document.GetElementbyId is not a function on line 496 of mootools.js of
    manager/media/javascript/mootools/mootools.js

    in Firefox but everything works ok in iE.


    What is happening is when i click to edit something instead of opening the document i clicked, it opens the root document of whatever im tryin to do.

    Like if i click to edit a template it always opens template 1, or snippet 1 or document 1, i have no clue what iv done to it and not even sure how long its
    been like this sad

    Anybody have any suggestions?
      • 5727
      • 160 Posts
      Did you mess around with the Web Developer Tool bar? Sometimes I disable Javascript for testing and I forget to put it back... just a thought
        Olivier Deland
        Montreal, Canada - Web Developer
        • 10487 MODX Staff
        • 1,535 Posts
        Quote from: ShawnC at May 10, 2007, 08:01 PM


        document.GetElementbyId is not a function on line 496 of mootools.js of
        manager/media/javascript/mootools/mootools.js
        This is a documented Firefox bug, not a MODx problem. I’ve never seen it cause the behaviour you describe though ... that’s weird :\ You sure there’s nothing else showing up (or anything you might have changed)?
          Garry Nutting
          Senior Developer
          MODX, LLC

          Email: [email protected]
          Twitter: @garryn
          Web: modx.com
          • 26964
          • 8 Posts
          Quote from: garryn at May 11, 2007, 04:08 PM

          Quote from: ShawnC at May 10, 2007, 08:01 PM


          document.GetElementbyId is not a function on line 496 of mootools.js of
          manager/media/javascript/mootools/mootools.js
          This is a documented Firefox bug, not a MODx problem. I’ve never seen it cause the behaviour you describe though ... that’s weird :\ You sure there’s nothing else showing up (or anything you might have changed)?

          well after futher playing with it, i noticed i dont always get that error so thats probably a unrelated error then. I probably changed something but im not sure what exactly i changed to do this thou as iv been editing modx alot then i got busy with freelance work so i stoped for a week or 2. and startd again so i kinda forgot whatever i mighta done to it lol.

          Its really odd that it broke in both the manager and frontend so im guessing it has to be something w/ the javascript librarys.

          ATM i still havent quite figured out what i did but im gonna keep looking and see if i can find whats going on with it.