I think that using the update child pages function does not install unique instances of the block in every page using that template. I think it simply creates a pointer to that single block instance in the template which is why every page is using the same instance of the block.

Is there a way work around that?

I think the short answer is no... however.. I will look at the block with a view to making it use the page ID rather than the block ID... this 'might' solve the problem.

Thank you Jimbo!

That would be awesome because anything else was perfect!!!!

Cheers,
Carl

Sorted.. V2 is now available.

I'm using v2 of this add on on v5.6 of Concrete.

When I add to the page type defaults the block and setup on child pages, I still have only one instance site wide rather than one instance per page.

What I am I doing wrong??

This is interesting. I actually like this add-on, it accomplish the task of voting really good. But as above, I can't seem to get it to work on blog pages. When voting on one, it votes on all. And I too do not see version 2.1 anywhere.
I have tried two different approaches. 1. adding it to the page type from a stack. 2. adding it directly on the page type directly. I a thinking on embedding it on the page type, and would appreciate the embed code if you have it.

Another thing - I think that it is so good that I would like to translate it to Danish. But I see that t() functions is missing.

Please tell me if you do support this add-on or if it is off your grid.

/Michael
Concrete5 Danmark