Skip to content

Instantly share code, notes, and snippets.

@kojiromike

kojiromike/gist:494a7995695495b8d2dd

Last active August 29, 2015 14:02
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save kojiromike/494a7995695495b8d2dd to your computer and use it in GitHub Desktop.
Save kojiromike/494a7995695495b8d2dd to your computer and use it in GitHub Desktop.
Download ZIP
Things I think the "Disable Modules Output" screen is useful for in Magento
Raw
gistfile1.md
  1. Being able to see effectively installed modules. Sometimes a module is unexpectedly installed (or not) and you want to be sure. If it's listed in this screen, you know it's installed.
  2. Being able to disable the frontend rendering of a module without turning off its code. This is useful when a module is a tight dependency or when you just temporarily want to shut something up. ;) I think it would be clearer if this feature were named something different, but naming things is a hard problem.
  3. Being able to enumerate all the modules. This differs from #1 in that it lets you get a general idea of the modules on a particular system (for example a production system) without needing shell access or taking any risky actions. (That said, being able to view installed modules shouldn't necessarily be the same permission as being able to disable their output.)

I know Magento 2 is working hard to strip out unnecessary tight dependencies between modules in core, but even if AdminNotification is optional, I can still see the above features being useful in core, particularly 1 and 3 above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment