Error in Tree.php

[stopsatgreen]

I've just upgraded from 1.2 to 1.3 and got a fatal error from line 624 of Tree.php. If I downgrade Tree.php to the version included in 1.2.5, there is no problem.

I'm running PHP 5.2.4, and everything else seems to be working.

[paul.warren]

For info I just upgraded three sites on the same server from 1.2.5 to 1.3.
Two sites worked fine, but one site gave error
Fatal error: Call to a member function Active() on a non-object in site/lib/Tree/Tree.php on line 624
Following stopsatgreen's suggestion I also downgraded Tree.php and the site now works fine
but of course it would be better to identify what was causing the problem....  how?

[acorn]

I have upgraded to 1.3 for several sites. Two had the same error in tree.php. One as an upgrade and the other was a fresh install.

I replaced the tree.php file with one from a previous CMS version. This solved the Tree error but I now have the following:

Fatal error: Call to a member function Id() on a non-object in /home/xxxx/public_html/plugins/function.breadcrumbs.php on line 119

- I tried replacing the file with the new and old version (no result)

Fatal error: Call to a member function Id() on a non-object in /home/xxxx/public_html/modules/Cataloger/Cataloger.module.php on line 361

- I have tried re-installing the Cataloger module (no result), I then uploaded the latest version of Cataloger (no result)

Can anyone help?

[stopsatgreen]

I've just upgraded another site from 1.2.4 to 1.3.1 and got the same error; although, curiously, not for all instances of {menu}; this worked:

Code: Select all

{menu items='contact,sitemap,gallery' template='List_Menu'}

This gave the error:

Code: Select all

{menu number_of_levels='2' template='List_Menu'}

Again, going back to a previous Tree.php solved the problem.

[hotaru]

I also just had the same issue - upgraded from 1.2.5 to version 1.3.1 and all seemed to go well. Went to my website and the pages stopped loading when they hit the menu. 

Found this thread and reverted to the tree.php from version 1.2.5, and everything works again. 

[Jack @ PharSide]

I just had the same issue too. Is this a caching issue? Any word would be appreciated as I will be testing everything until I hear from someone.

Cheers,
-Jack

[RonnyK]

This was an issue in earlier releases..... I havent heard about this issue on the 1.4 series...

Why dont you use the latest, being 1.4.1 atm

Ronny