Is there any way, at the code level, to determine which parts of a View use AJAX and which don't? It's a reasonable UI decision, but does not seem to reflect an underlying code reality, that AJAX is all or nothing. It seems it should be possible to disable it per component.

The immediate issue: We have a View where Exposed filters using AJAX are not working. Exposed filters work if AJAX is disabled for the view. Unfortunately AJAX is a global setting and we need AJAX for Views Load More (which might well be the cause of the conflict that breaks AJAX filtering, of course). If AJAX could be turned off just for the exposed filter, it seems that would work well.

Thoughts / direction? Thanks!

Comments

merlinofchaos’s picture

merlinofchaos commented

Unfortunately you are correct; AJAX is an all or nothing thing on a view, and there isn't any concept of components using AJAX in a way that the system understands it. There is just a single flag, and 99.99% of the time, that's all that's needed.

In your case, you may be required to set up a snippet of javascript that utilizes the AJAX only for the bit you want. I'm not at all familiar with the ajax views more module, and indeed it may be interfering.

mustanggb’s picture

mustanggb commented
Issue summary: View changes
Status: Active » Closed (outdated)

Closing this as outdated to tidy up a bit around here. If you're still having problems with the latest release please create a new issue.