Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
We need to be able to let users show menus in the sitemap, but have different titles than what shows up by default where the menu actually exists. We would like a "sitemap title" option on the menu edit form so that they can specify a title to use specifically for that page.
Comment | File | Size | Author |
---|---|---|---|
#1 | sitemapmenutitleoverride.patch | 2.12 KB | camprandall |
Comments
Comment #1
camprandall CreditAttribution: camprandall commentedI have a minor patch that adds a sitemap menu title field to the edit menu form, saving the results in variables, and then shows the alternate title on the sitemap configuration form as well as the sitemap itself.
Comment #2
vikramkanav CreditAttribution: vikramkanav commentedComment #3
vikramkanav CreditAttribution: vikramkanav commentedHi Campradll
I used your given patch but its does not over ride the title sitemap menu. Please tell the solution for it.
Comment #4
daffodilsoftware CreditAttribution: daffodilsoftware commentedHi Vikram
Its working fine . We have reviewed the patch given by camprandall. There is no issue in it.
Comment #5
vikramkanav CreditAttribution: vikramkanav commentedI agree the patch is working it was my mistake.
Comment #6
camprandall CreditAttribution: camprandall commentedI'm updating this to "reviewed and tested" since multiple people have verified that it works.
Comment #7
darrell_ulm CreditAttribution: darrell_ulm commented@frjo another one, should I incorporate to dev and push it in? Thanks!
Comment #8
colanCoding standards: Missing space before the sentence and punctuation after. See https://www.drupal.org/coding-standards.
Missing whitespace around the ".".
Would probably be better to use hook_form_FORM_ID_alter(). Also, missing "().".
Missing punctuation.
Finally, new variables are being adding without being deleted in hook_uninstall().
Comment #9
colanActually, what about having a single variable (array) to store all of these? Then we could declare it with the Variable module, and wouldn't have to worry about uninstalling? See #1545422: Expose configuration options to variable module to enable per language settings for an example.