Could you post this in the bugs tracker? This really should work regardless..

Did you found a temp. workaround for that?

greets Marv

I thought Andrew fixed that method in the 5.3 release?

I didn't check tho...

I just came across this today!
Same issue, so no it isn't fixed in 5.3.1.1

Would really appreciate it if it would work somehow.

(and no I didn't found a workable workaround, manually coding each time for a new page isn't really what I had in mind.)

reading trough the area.php i found the hint for passing the page object. So the only little correction on Remo's code is:


greets, Marv

tho >.< yeah..

I also tried $a->totalBlocks, but that returned nothing usable. Now it works for me too.

cool! thanks for sharing

Looking at the code, it would make much more sense if the page object is mandatory in the getTotalBlocksInArea() method, because then there wouldn't be any confusion. It makes sense to us as developers that it should be mandatory, because the area object doesn't know which page its supposed to be querying, but it should then just be made mandatory in this call.

Will get that in there for the next release - but in the meantime yeah, just pass the page object into this method and it should be accurate.

I'm going to backpedal on this. There's a lot of code out there that assumes that the page object is not passed - and in many cases it doesn't need to be (since the getAreaBlocksArray method has already been run.)

So this method is probably going to stay the same as it has been. We'll just make a note that, when theme and template builders are using this method, they really need to pass the page object through.