I'm using Better Exposed Filters with a views pane which is included in a panel node to filter the contents via AJAX. I have fields exposed to the content managers of panels to be excluded, which works great until an end-user (anonymous or authenticated) selects an item on the rendered page and the result is fetched via AJAX. At which point, all field exclusion is ignored. I have tried passing the filter value as a query string and it works fine, but as soon as a views AJAX request is sent the exclusion is no longer honored.

Comments

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Closed (won't fix)

Unfortunately this is a known, unsolvable issue. When you set up a view in Panels, and have Panels change the configuration, and then use Views' built in AJAX, all of Panels' changes to the view are ignored, because the panel isn't involved at all in the ajax process.

amaisano’s picture

amaisano commented
Issue summary: View changes

Lame workaround: in the "real" View config/settings for that view pane with AJAX, exclude the fields you don't want to show up on subsequent AJAX requests by default. The visit on the page will respect the panel's view pane field display checkboxes, and the subsequent AJAX refreshes for that view will respect the view.