You are here

UPGRADE.txt in Nice Menus 7.3

Same filename and directory in other branches
  1. 5 UPGRADE.txt
  2. 6.2 UPGRADE.txt
  3. 6 UPGRADE.txt
  4. 7.2 UPGRADE.txt
NICE MENUS UPGRADES
===================
5.x, 6.x-1.x ---> 6.x-2.x
-------------------------
There is an update hook and you should run update.php to get things moved 
around properly. Aside from the minor database changes, there are a number of 
things you should be aware of, especially in light of any customizations you 
may have made.

THEME FUNCTIONS:
The theme functions have all been RENAMED to be more in line with Drupal 
standards, so if you are overwriting the functions in your theme's 
template.php or calling the functions anywhere in your theme, you should 
update the function names. The old functions were called theme_nice_menu_* and 
the new ones are theme_nice_menus_*, with an "s" to match the module name.

NEW JAVASCRIPT:
The old JS has been completely removed and replaced with JS that uses the 
Superfish jQuery plugin. It now fires for ALL browsers by default, unless you 
turn the JS off in your settings at Administer > Site configuration > Nice 
menus (admin/build/nice_menus). If you had "Enable IE support" checked under 
older versions of NM, then the new JS will be on by default. If it was 
unchecked in your older version, then the update will turn JS off for you by 
default. If you turn JS off on the site (or a visitor comes without JS 
enabled), IE6 will no longer get the dropdown effect, but all other browsers 
will fall back to CSS-only dropdowns.

CSS IDs and CLASSES:
The menu-$menuid ID has been changed to a CLASS to avoid invalid HTML when 
displaying the multiple menus which use the same menu ID. If you have custom 
CSS that depends on the menu ID then you need to change it to a class. For 
example:
  #menu-3 {color: #ff0};
would need to be changed to
  .menu-3 {color: #ff0};
  
IE-Specific Class removed
The legacy "ie-over" class which was added for IE compatibility in the past 
has been replaced with a generic, non-browser-specific, "over" class since 
this is used by Superfish and should be general.

5.x ---> 6.x
------------
Due to the menu system changes from 5 to 6, when you upgrade Nice Menus, your 
blocks will "forget" what menu they were set to. So take note of the blocks 
and menu settings prior to upgrade, then reset them after the upgrade. See the 
issue at http://drupal.org/node/524688 for more information.


4.7 ---> 5.x
------------
The CSS class has changed to change the underscore (_) to a dash (-)
The 4.7 version of class="nice_menu" is now class="nice-menu" in version 5.
You will need to adjust any Custom CSS you have added to account for this.
The default CSS that comes with nice_menus uses this new convention already.

Also note that the layout CSS for the module has been broken out into a
separate CSS file (nice_menus_default.css). You have the option of replacing
this file by creating a separate customized CSS file, and overriding the
default CSS file at Administer -> Themes -> Configure -> Global settings ->
"Path to custom nice menus CSS file".

File

UPGRADE.txt
View source
  1. NICE MENUS UPGRADES
  2. ===================
  3. 5.x, 6.x-1.x ---> 6.x-2.x
  4. -------------------------
  5. There is an update hook and you should run update.php to get things moved
  6. around properly. Aside from the minor database changes, there are a number of
  7. things you should be aware of, especially in light of any customizations you
  8. may have made.
  9. THEME FUNCTIONS:
  10. The theme functions have all been RENAMED to be more in line with Drupal
  11. standards, so if you are overwriting the functions in your theme's
  12. template.php or calling the functions anywhere in your theme, you should
  13. update the function names. The old functions were called theme_nice_menu_* and
  14. the new ones are theme_nice_menus_*, with an "s" to match the module name.
  15. NEW JAVASCRIPT:
  16. The old JS has been completely removed and replaced with JS that uses the
  17. Superfish jQuery plugin. It now fires for ALL browsers by default, unless you
  18. turn the JS off in your settings at Administer > Site configuration > Nice
  19. menus (admin/build/nice_menus). If you had "Enable IE support" checked under
  20. older versions of NM, then the new JS will be on by default. If it was
  21. unchecked in your older version, then the update will turn JS off for you by
  22. default. If you turn JS off on the site (or a visitor comes without JS
  23. enabled), IE6 will no longer get the dropdown effect, but all other browsers
  24. will fall back to CSS-only dropdowns.
  25. CSS IDs and CLASSES:
  26. The menu-$menuid ID has been changed to a CLASS to avoid invalid HTML when
  27. displaying the multiple menus which use the same menu ID. If you have custom
  28. CSS that depends on the menu ID then you need to change it to a class. For
  29. example:
  30. #menu-3 {color: #ff0};
  31. would need to be changed to
  32. .menu-3 {color: #ff0};
  33. IE-Specific Class removed
  34. The legacy "ie-over" class which was added for IE compatibility in the past
  35. has been replaced with a generic, non-browser-specific, "over" class since
  36. this is used by Superfish and should be general.
  37. 5.x ---> 6.x
  38. ------------
  39. Due to the menu system changes from 5 to 6, when you upgrade Nice Menus, your
  40. blocks will "forget" what menu they were set to. So take note of the blocks
  41. and menu settings prior to upgrade, then reset them after the upgrade. See the
  42. issue at http://drupal.org/node/524688 for more information.
  43. 4.7 ---> 5.x
  44. ------------
  45. The CSS class has changed to change the underscore (_) to a dash (-)
  46. The 4.7 version of class="nice_menu" is now class="nice-menu" in version 5.
  47. You will need to adjust any Custom CSS you have added to account for this.
  48. The default CSS that comes with nice_menus uses this new convention already.
  49. Also note that the layout CSS for the module has been broken out into a
  50. separate CSS file (nice_menus_default.css). You have the option of replacing
  51. this file by creating a separate customized CSS file, and overriding the
  52. default CSS file at Administer -> Themes -> Configure -> Global settings ->
  53. "Path to custom nice menus CSS file".