-
-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move creating of nav & menu items to legacycustomsearches extension #23862
Conversation
(Standard links)
|
'operator' => 'OR', | ||
'separator' => 0, | ||
]); | ||
_legacycustomsearches_civix_navigationMenu($menu); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI. We have several ways for extensions to add to the nav menu, and none of them are very good:
- Insert during installation (
hook_civicrm_install
) using the api - Use
hook_civicrm_navigationMenul
- Use
managed
They all have downsides. 1 requires manual cleanup during uninstall, and manual handling of multi-domains. 2 is non-configurable, frustrating admins who want to customize their menus. 3 works well as long as you loop through the domains in the .mgd.php
. So on balance I think 3 is my favorite, and I've recently started using this pattern:
@eileenmcnaughton this looks good except for the test failures :/ |
@colemanw I fixed the test failure that seemed to relate - hopefully this will pass now - would be good to get a MOP so I can merge if it does since it now contacts a |
@eileenmcnaughton still some test issues |
10b8c6c
to
de9402f
Compare
Overview
Move creating of nav & menu items to legacycustomsearches extension
Before
Menu & navigation items for legacy custom searches declared in core code
After
Declared in the extension
Technical Details
As part of making it turn-offable....
Comments