Inactive child pages break MenuManager, again on 1.10.1?!

[hibr]

Sorry to bring this again.

The error:

Code: Select all

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

appears, when you click on a menu item which has an inactive child. The error appears on the following menu item either.

In http://forum.cmsmadesimple.org/viewtopi ... 74&t=56358 this 1.10-beta-issue should be fixed in 1.10 final release. In fact in 1.10 this issue did not appear as promised. But this error reappears on my sites after updating from 1.10 to 1.10.1! I used the diff-update archive.

Kind regards,

Hani

[cnymike]

I also got this error

Code: Select all

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

I have an inactive child page and when made active the error goes away. Make it inactive again and the error appears.

I did not upgrade via the diff however, I did a full new install of 10.10.1 over 1.9.4.2

[wuppl]

I also got this error too

Code: Select all

Call to a member function Active() on a non-object at modules/MenuManager/MenuManager.module.php:254 	

The same: I have an inactive child page and when made active the error goes away. Make it inactive again and the error appears.

[cnymike]

Right. And the implications of this error is that I have at least 5 client websites right now that have been upgraded to 1.10.1 and they all have inactive child pages that are throwing this error.

The child pages cannot be deleted because they are rotated in and out of inactive status at varying times throughout the year. So basically all my client sites are broken.

Very very frustrating that no fix has been made yet.

[gianpiero]

I had one child inactive was breaking the menu.
I copied/pasted the father/mother of that page.
I moved other child ( active ) under new father/mother

It worked for me. It's only a workaround solution,
waiting if anything has to be fixed

bye, /gp

[wuppl]

I solved the problem in this way:

I have copyed a new 1.10.1 version over the old 1.10.1 installation. I think, that there is a bug in the diff 1.10 to 1.10.1

greetings from Lübeck (DE)
wuppl

[gianpiero]

I think, that there is a bug in the diff 1.10 to 1.10.1
wuppl

I think no, because I upgraded from 1.9.4.3 to 1.10.1 full version directly and the bug happened
bye
gp

[cnymike]

I also did a full upgrade from 1.9.4.2 to 1.10.1.

What I have not yet done is a full reinstall to see if that might fix things.