We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 30498
    • 30 Posts
    In the process of writing a custom module I noticed how at the end of my formlet (produced by the module) mootools is included. I don't want/need that and browsers are throwing errors because it gets attached after the </html> tag. Whats worse, internet explorer 8 stops handling other scripts because of it.

    Here's what im seeing at the end of my closing hmtl tag:
    <link rel="stylesheet" type="text/css" href="/manager/media/style/MODxCarbon/style.css" /><script type="text/javascript">
    // <![CDATA[
    window.addEvent('domready', function() {
    var sysAlert = new Element('div').setProperties({
    'class': 'sysAlert'
    });
    sysAlert.innerHTML = '<div style=\'margin-left:10px;margin-top:3px;\'><span style=\'color:maroon;\'><b>Course Modules - Module runtime error:</b></span>

    An error occurred while loading the module. Please see the event log.</div><hr sys/>';
    var boxHtml = new MooPrompt('System Alert', sysAlert, {
    buttons: 1,
    button1: 'Ok',
    width: 500
    });
    });
    // ]]>
    <

    Nowhere in my module am I calling mootools. So the question is... What is it that adds this junk to my module, eventhough I didn't call it anywhere and more importantly.... How do I get rid of it?
      • 4310
      • 2,310 Posts
      Mootools is part of the Manager frameset, so is always present, but doesn't affect the module code.
      That's a warning that you have a run time error with your courses module, which when fixed would disappear.
        • 9995
        • 1,613 Posts
        *I think their are busy completely removing mootools with Clippercms
          Evolution user, I like the back-end speed and simplicity smiley