Here is a small patch that allows modules to add to the querystring of an item.
Case: I have used this to allow CiviCRM use standard menu entries for it's functions instead of the custom block that is currently being used. I am going to submit a patch for the next version of CiviCRM which will remove the current blocks and use the Drupal menu structure which is more powerful.
The attached patch was created on 4.7.2 but should apply to CVS.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | civicrm_menu.patch.txt | 9.14 KB | gordon |
| #3 | menu_doc.patch.txt | 814 bytes | gordon |
| menu_query.patch.txt | 770 bytes | gordon |
Comments
Comment #1
dries commentedCommitted to CVS HEAD.
(Looks like a stupid function to me.)
Comment #2
gordon commentedJust out of interest, what is the stupid function. adding the query parameter, or the theme_menu_item() function.
Comment #3
gordon commentedHere is the changes to the api for hook_menu()
Comment #4
morbus iffGordon - thanks for this! I was just remarking to myself how annoying it was that I couldn't use query strings (for, yes, the reset=1 of a CiviCRM menu item that I was manually making into my own Drupal block). Wunderbar!
Comment #5
gordon commentedNP, my client also found this annoying. I know that this is not really related, but for interest here is that patch to CiviCRM 14. which puts all the menus in the menu.
It does remove from the blocks, but they can be another change.
Comment #6
Amazon commentedI have been testing out query strings with CiviCRM in Drupal 5. I am unable to use query strings with menu items. Could someone shed some history on what was committed and if there was another patch that removed this ability.
Comment #7
brunodboComment #8
brunodboChanged the component to reflect the new component categorization. See http://drupal.org/node/301443.
Comment #9
catchMarking this very old and miscategorised issue as fixed.