Currently any element that matches the select statment in the jquery is ajax-ified, including pagers that are unrelated to the ajax-ified view.
So the request is to add a way to exclude pagers (etc.) from being ajax-ified when under an ajax-ified view.
from
.find('ul.pager > li > a, th.views-field a, .attachment .views-summary a')
to
.find('ul.pager:not(.exclude) > li > a, th.views-field:not(.exclude) a, .attachment .views-summary:not(.exclude) a')
I don't see it as interfering with anything currently unless exclude is being used for some other purpose, but I doubt that (in that case, maybe ajax-exclude would be more appropriate).
Currently the only way to do it is change the classname from pager to something else, and re-themeing for the new class, which annoys the themer and makes the css a bit messy with duplication.
(I love how views provide all those possible theme functions for pagers, btw :>).
| Comment | File | Size | Author |
|---|---|---|---|
| views_exclude.patch | 687 bytes | hefox |
Comments
Comment #1
dawehnerUpdate status.
Comment #2
merlinofchaos commentedHmm. I am not sure that adding a class to the other pagers is really the right way to go about this. It seems like we should be adding a class to our own pagers and ajaxifying that instead?
Comment #3
merlinofchaos commentedComment #4
esmerel commentedNo updates to patch in more than 3 months.