Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Is there a category for 'nitpicky'? :) Some superfluous stuff may appear when modules such as blog, taxonomy or book aren't enabled. This patch just inserts the necessary checks and moves the $form items into them. Same issue in D6 version but may not be important enough to fix (but do let me know if you want a patch for that, too).
(I'm new to patches so let me know if it isn't exactly right.)
Comment | File | Size | Author |
---|---|---|---|
site_map-admin_settings_form.patch | 6.97 KB | Ellen Dee | |
Comments
Comment #1
frjo CreditAttribution: frjo commentedI'm uncertain what is the best here.
Hiding them as you suggest is cleaner but showing them makes it easier to see what features the module can offer.
Does someone else have some comments or suggestions about this?
Comment #2
Ellen Dee CreditAttribution: Ellen Dee commentedI think it's always confusing to be offered features when they aren't really available, especially to new users. I concur with what you're saying, though. How about instead disabling (rather than hiding) elements and providing messages to indicate that more features are available if x modules are enabled?
Here's an idea:
Break out the module-dependent stuff into their own fieldsets under SITE MAP CONTENT. While we're at it, bring the CATEGORIES SETTINGS stuff into the SITE MAP CONTENT fieldset, since it affects how the category content is generated. (Not sure about RSS SETTINGS, since I've never used it and I'm not sure what it does.)
So you would end up with:
Thoughts?
Comment #3
andypostI think it's better to show this options as disabled and use D7 states to show advanced options when user set checkbox (fieldset seems bad idea)
Comment #4
andypostAgree with Lara!
After looking into code I think that better to reorganize settings form - make menu tabs: General, Content, Taxonomy, Book
Once a module enabled the menu is rebuilded and user could change settings for sitemap but while book or blog disabled the settings just stores a useless variables in memory and confusing user with a huge settings form without any reason.
Suppose users read a module page before module download
PS: signature should be changed according http://drupal.org/node/224333#hook_forms_signature
Comment #5
andypostFiled different issue about function signature #1107786: Fix admin settings form definition
Comment #6
darrell_ulm CreditAttribution: darrell_ulm commentedLooking at this, new feature set should be able to give this option and some other types of flexibility.
Comment #7
darrell_ulm CreditAttribution: darrell_ulm commentedHi, quick test of the patch above on the 7.x dev branch does not apply at this point, but as per the discussion not sure this is going to happen the way the patch proposed anyway.
Just an FYI
Thank you
Comment #8
daffodilsoftware CreditAttribution: daffodilsoftware commented@darrellulm I could see that these checks are already committed to the dev branch.So I am making it closed