-
-
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
Menubar - Improve flexibility & remove hardcoded values #14839
Conversation
(Standard links)
|
@AkA84, any chance you'll be able to look at this? |
AkA84 tested this & approved it on the gitlab issue. Looks to be merge ready. |
It would be good to see an |
@colemanw I am unsure about the 'non-civicrm' is that a Drupal Only thing? In WP the menu looks fine after applying the patch. I do think the only way to really test this in the wild is to merge it and monitor the 5.17 RC. |
Merging based on @kcristiano comments |
@kcristiano yes there is a drupal module to display the Civi menubar on selected non-civi pages. It wouldn't be hard to create a WP plugin to do the same. |
Included in CiviCRM 5.16.0 Core PR: civicrm#14839 Gitlab Issue: https://lab.civicrm.org/dev/core/issues/1127
@colemanw what version is this PR going to be in? 5.16 or later? |
Ok I've opened up a backport PR. |
Overview
Minor tweak to
crm.menubar.js
to make it less reliant on the presence of a<div id="crm-container">
which may not be present on non-civicrm pages.Also tweaks the js to remove hardcoded pixel values to work better with theme overrides.
Before
Problems loading on non-civicrm pages.
Hardcoded values interfere with theme overrides.
After
Works better on non-civicrm pages.
Works better with theme overrides to the menu size & breakpoints.
Comments
Fixes https://www.drupal.org/project/civimenu/issues/3068607
Fixes https://lab.civicrm.org/dev/core/issues/1127