Don't Override BlockController Constructors in 5.4.0.6+
Permalink
just a quick warning. i was just testing out some of my blocks against 5.4.0.6, and it seems like the BlockController constructor must now be run for block's to operate. so if you're running any initiation stuff in the constructor, make sure you're calling parent::_construct() too.
Is this the way it should be? Why the change?
I think this may have been an issue for awhile, but I think I actually solved it in subversion. However, there are other issues with that code, so I've backed it out and am moving it into the 5.4.1 branch (which I have to work on anyway.)
So you shouldn't actually have to change your block's code at all at this point, or really actually ever. When these changes do get moved in they'll be optional caching improvements that, if blocks don't support by declaring some protected variables in their controller, they'll behave just like they always have.
So you shouldn't actually have to change your block's code at all at this point, or really actually ever. When these changes do get moved in they'll be optional caching improvements that, if blocks don't support by declaring some protected variables in their controller, they'll behave just like they always have.
