[fixed] Inactive child pages break MenuManager

[scooper]

After an upgrade of a dev site from 1.9.4.2 to 1.10-beta1 we had an error on the frontend:

Code: Select all

Fatal error: Call to a member function Active() on a non-object in /home/betatest/public_html/modules/MenuManager/MenuManager.module.php on line 254

Those lines in MenuManager refer to a check for whether menu items have children but fall over when we have a child page set to inactive in our content list.

Making that child page to active gets rid of the error and this error doesn't appear if a top level page is set to be inactive.

Fantastically annoyingly we have a couple of child pages which can be made inactive without this error but it's repeatable with newly added pages and the majority of child pages. Let me know if you need me to investigate further or need access.

[Rolf]

Yep, reproduced in both beta1 and latest SVN.
Good catch!!

When first child is set inactive and open the parent page:
Fatal error: Call to a member function Active() on a non-object in C:\www\svn110x\modules\MenuManager\MenuManager.module.php on line 254

®

[Rolf]

fixed in svn rev.7362