That analysis is correct Lisa. We should just remove those DEEVMODE_ options as they don't do anything anymore for the mochikit part (as it is gone) and if people want special devmode css they can add it to their css/sass files rather than having a dedicated htdocs/theme/debug.css file
-- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1835681 Title: Check if we still need the config parameter "developermode" Status in Mahara: In Progress Bug description: There is the config.php parameter "developermode". It says in /lib /config-defaults.php: * @global int|bool $cfg->developermode Developer mode * When set, the following things (among others) will happen: * * * 'debug.css' will be included on each page. You can edit this file to add * debugging CSS at your discretion * * the unpacked version of MochiKit will be used * * These options are a performance hit otherwise, enable when you are * developing for Mahara */ $cfg->developermode = false; // $cfg->developermode = DEVMODE_DEBUGCSS | DEVMODE_UNPACKEDJS; --- It would need to be checked what "among others" is. We are not using debug.css and Mochikit has been removed. Before we get rid of the parameter though, it would need to be checked if removing it impacts anything else. Once the analysis is available, we can make a decision. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1835681/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
