Forums

AutoNav-related Upgrade Error - Why?

Permalink
I just upgraded to 5.4.0.5 from 5.4.0, and I now get a fatal error...

Fatal error: Call to undefined method AutonavBlockItem::setName()

I have a modified header_menu.php template installed, and it has been working fine until the upgrade. I am making a call to the method referenced in the error. What I don't understand is that the method does exist in the AutoNav controller; so why am I getting this error?

-Steve
Shotster
 
Shotster replied on at Permalink Reply
Shotster
Upon further investigation, it appears I added that method; but I still don't understand why it says it's undefined.

-Steve
Shotster replied on at Permalink Reply
Shotster
Ok, the problem was that I didn't understand how updates worked. After looking things over, it's now clear that no files are overwritten. Instead, a complete C5 installation is downloaded to the updates directory, and a new constant referencing the installation path is added to site.php.

Until now, I'd been updating via SVN, so I had not encountered this before. I think I understand now. (It also makes it easy to roll back to a previous version.)

-Steve
Shotster replied on at Permalink Reply
Shotster
And oh yeah, I should certainly not have modified the core controller file for autonav. I don't recall doing that, but it should have been overridden instead.

-Steve
Shotster replied on at Permalink Reply
Shotster
Now that I [think I] understand updates, how will it work over the long run? I mean, if an entire C5 installation is added with each update, that could eat up a lot of disk space quickly. What's the plan for dealing with accumulating updates? Should they be purged manually as needed?

Also, I'm still curious about the SVN repository. The latest C5 version does not yet appear there. I had established an update protocol using the SVN "switch" command. Are updates no longer being made available via SVN?

Thanks for the help,

-Steve