Allow site administrators to select whether or not they want a module enabled for particular content types AND for different tabs in that content type - for example disable module altogether for a content type that doesn't use it, or disable module for 'view' tab because it is only needed in edit.

Sounds weird, but could give a high degree of granularity when dealing with developing modules and allow for more precise tuning of a site

Comments

RobertPope’s picture

RobertPope commented
Title: Disable nodes based on content type/tab » Disable modules based on content type/tab

fixing a typo

damien tournoud’s picture

damien tournoud commented
Status: Active » Postponed (maintainer needs more info)

What is a "module" for you? I'm not really sure I understand your proposal.

RobertPope’s picture

RobertPope commented

envisionment - adds a tab to each content type that says 'modules' - when clicked you see a list of modules running down the left, the modules that are not used for that node at all are grayed out and unselected. There is a row across the top that says 'view' and 'edit'. You can unselect modules for the content type and they will behave as disabled for that content type or that view of the content type (view or edit).

sun.core’s picture

sun.core commented

Please provide concrete examples.

mdupont’s picture

mdupont
Primary language French
Location Switzerland
commented
Component: admin.module » ajax system
Status: Postponed (maintainer needs more info) » Closed (won't fix)

The right way to do it wouldn't be to pseudo-disable modules by content type, but it is rather either to configure the modules properly, or to alter the way the module works through a custom module (to show / hide elements on the view or edit form). Closing.

mdupont’s picture

mdupont
Primary language French
Location Switzerland
commented
Version: 7.x-dev » 8.x-dev
Component: ajax system » base system