I am writing a display extender for http://drupal.org/project/metatags and found the process of enabling a display extender a little confusing, even for myself. It's buried under the 'Advanced' sub-tab of the 'Settings' page which will be big and scary for my end users to wander into. I can automate enabling my extender using hook_enable() and hook_disable() but it means my extender has to be its own separate module and can't be merged into a larger code base (which might be a good thing).
It would be nice if I could specify I want my extender enabled by default, or make this process easier for end-users.
Related: #1279182: Disabling a module with a display extender causes WSOD errors
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 1279202.patch | 2.18 KB | dawehner |
Comments
Comment #1
dave reidAdding tag.
Comment #2
dawehnerThis patch allows to force the dispaly extender to be enabled, do you think this makes sense?
Currently views_chuck does add a (forced) string to the title to show this, perhaps views should show in the advanced tab which extenders are required.
Comment #3
dawehnerJust commited as it is, for further improvements a follow-up can be created.
Comment #4
mustanggb commented