CSS broken after update/migration
Jamroom Developers
Developer mode works like this:
Quote: Enabling the "Run in Developer Mode" option will change the information displayed in the "Info" tab for a module to include information about Module Triggers and Listeners, as well as force all template and cache items to be built on every access.
Warning: Enabling Developer Mode will make your system run much slower than normal!
Default: off
Template Variable: {$_conf.jrDeveloper_developer_mode}
Warning: Enabling Developer Mode will make your system run much slower than normal!
Default: off
Template Variable: {$_conf.jrDeveloper_developer_mode}
That is in the inline help button next to the "run in developer mode" checkbox in jrDeveloper global config. It's the on/off switch which is the first item in jrDeveloper config and you need to check that box in order to run in developer mode. I count that as pretty good notification because I always read the inline help when installing a new module.
If you are already adding the files in meta then all is fine. You only add them through the core if you need them to be minified for you, (you can always add a pre-minified version if you want to reduce the number of calls from meta.tpl, there will be no comments removed).
The main benefit of adding them through the core is that when you format those comments correctly they are used to automatically add user editing of the css in the skin editor - that's the really cool part!!! Check it out! It's an awesome (and easy) way to make your 3rd party css editable in the jamroom acp.
updated by @ultrajam: 02/17/14 12:16:10PM