WordPress version 4.4 changed the way the menu structure was returned when using a custom menu. The symptom is that a menu item before a menu with a submenu would show an indicator that there were child items, while the actual parent of the submenu would not show the indicator.

To fix this problem you can eithor (1) edit bfa_new_wp3_menus.php and change line 43 from

	$newmenu = preg_replace("/<li (.*?)class=\"(.*?)\">(.*?)\n(.*?)<ul class=\"/i","<li \\1 class=\"rMenu-expand \\2\">\\3\n\\4<ul class=\"rMenu-ver ",$newmenu);

to

	$newmenu = preg_replace("~menu-item-has-children~","rMenu-expand menu-item-has-children",$newmenu);

or (2) download the attached file, unzip it and replace bfa_new_wp3_menus.php with the fixed version.

Good fix! Thanks Juggledad!

Do you know many ATA versions back this fix will work for?

The code is the same all the way back to 3.7.15 - maybe earlier, but that's the earliest I had on my maching to check with.

Perfect!

Merci!!!

Originally Posted by jugglerdad

WordPress version 4.4 changed the way the menu structure was returned when using a custom menu. The symptom is that a menu item before a menu with a submenu would show an indicator that there were child items, while the actual parent of the submenu would not show the bathmate indicator.

To fix this problem you can eithor (1) edit bfa_new_wp3_menus.php and change line 43 from

	$newmenu = preg_replace("/<li (.*?)class=\"(.*?)\">(.*?)\n(.*?)<ul class=\"/i","<li \\1 class=\"rMenu-expand \\2\">\\3\n\\4<ul class=\"rMenu-ver ",$newmenu);

to

	$newmenu = preg_replace("~menu-item-has-children~","rMenu-expand menu-item-has-children",$newmenu);

or (2) download the attached file, unzip it and replace bfa_new_wp3_menus.php with the fixed version.

I haven't updated wordpress in a long time. If I update wordpress and update to the latest version of Atahualpa will there be a problem with the menus or is this fixed in the latest version?

this patch still applies to teh latest version of Atahualpa