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.
Between version 2.1 and 2.5 the directives to add the JS and CSS to the page were moved OUT of a hook_init function into a custom function. This breaks basic/core drupal themeing abilities and doesn't allow a theme a chance to override the CSS of the module by replicating the CSS files in the module (http://www.drupalcoder.com/blog/overriding-css-stylesheets-in-drupal-the...).
Comments
Comment #1
Perignon CreditAttribution: Perignon commentedThis function should be restored to follow drupal coding standards for themeing:
Comment #2
xiukun.zhou CreditAttribution: xiukun.zhou commentedthanks Perignon.
if move all js and css to
hook_init
. then will load nice_menu css and js in the all page.@see #2020617: CSS Conflict: Path to custom Nice menus CSS file loads css file in admin theme
Comment #3
Perignon CreditAttribution: Perignon commentedI bet if a use case analysis were done it would show that most every website using nice_menu's loads menu's on every page of the site. So that probably isn't that big of an issue.
This upgrade broke the CSS on my site when I performed the upgrade. Took me a few minutes to realize what happened when I finally dug into the module code to see that the hook_init was removed.
Comment #4
xiukun.zhou CreditAttribution: xiukun.zhou commentedhi Perignon,
But it should not be in the admin theme #2020617: CSS Conflict: Path to custom Nice menus CSS file loads css file in admin theme
Comment #5
apaderno