due to some odd ajax pagers behavior, i've discovered that the $dom_id is not being incremented when nodecomment blocks are displayed.

this means i have views blocks with duplicate dom-id classes on my page, which is causing the ajax errors.

the dom id is normally incremented in views/theme/theme.inc line 128 - template_preprocess_views_view(). for some reason it looks like the views preprocess function is not even being called by nodecomment when rendering it's block.

in order for ajax pagers to work properly on a page with nodecomments, $dom_id must be incremented. we will be submitting a patch soon.

Comments

tom_o_t’s picture

tom_o_t commented

Confirmed this issue on a couple of sites now.

jrefano’s picture

jrefano commented

this issue can be resolved by disabling views caching for nodecomment blocks, but i think that means there's still a bug somewhere...

crea’s picture

crea commented
Version: 6.x-2.0-beta3 » 6.x-2.x-dev

Well, disabling the cache is a workaround which can't be considered as a proper fix for the bug. We should investigate and fix the root cause of the problem.

angelmax’s picture

angelmax commented

subscribe

crea’s picture

crea commented

I remember I saw similar problem in the Views queue. I think it could be a Views bug, not Nodecomments' one.

crea’s picture

crea commented

#655002: 2 separate ajax views on a page => results updated in both places.

crea’s picture

crea commented
Status: Active » Closed (duplicate)