version 1.2.6 breaks site

Just as a heads up I have duplicated the issue, though I still can’t see how its happening. In reality I think it was bugged before, and due to non strict comparisons was somehow breaking in a useful way.

And once we added strict comparisons it caused them to work as initially intended.

To be honest looking at the original logic, there was no consideration made for hiding children of an excluded parent item. Otherwise it may mean it worked in previous versions of WP and they changed something but I can’t see that.

Stepping through every changed line now and seeing what is changing the outcome, will keep you posted.

Lol, I was both right and wrong. v1.2.7 just pushed.

A) The logic does contain a line to exclude children of an excluded item. Overlooked it before in a sea of red/green diffs.

B) It was in fact a bug that got fixed, and now is not properly matching.

			$exclude = in_array( $item->menu_item_parent, $excluded );

Was changed to include the strict comparison option which is generally a safer move.

			$exclude = in_array( $item->menu_item_parent, $excluded, true );

In this case $excluded is an array of integers and $item->menu_item_parent is a string which ends up always failing to find a match in the array.

Changing it to force menu_item_parent to be an int worked.

			$exclude = in_array( (int) $item->menu_item_parent, $excluded, true );

@danieliser,
i confirm that the issue is fixed in 1.2.7.
Thank you for giving us some of you time ??