I have ten views on one page (I have used panels to output this page). When I am changing a sort criteria by exposed filter in one area it is ok but when i am changing sort criteria in another view on the same page, first view is sorting by the second view sorting criteria...

Comments

merlinofchaos’s picture

Title: sorting in mulitple views on one page » Ability to change exposed sort identifier
Category: bug » feature

There appears to be no way to changed the exposed sort identifier which would allow these views to work more or less independently.

That said, with that many views on the page, you probably would rather use AJAX (turn on the ajax setting). Even if you do get this working, the forms won't affect each other; so when you change one view, the other will revert to their default values.

10 views per page is a LOT. It's going to be a very slow page without caching, and it's going to be a very *busy* page for users.

MStrzelecki_’s picture

I have got AJAX on already. But, view which was used (without page reload) fallows sorting criteria another view.

MStrzelecki_’s picture

plz add exposed sort identifier to 3.0 final :)

bib_boy’s picture

yes, i spent ages wondering what was wrong until I read this. I have 2 views with exposed filters in a panel pane and when I filter on the bottom view the top view displays the default as you suggest. Unfortunately the default is the 'Any' option so i end up with multiple results for the top view which the user did not filter on. So it becomes confusing for the user if they are filtering on the view below and get a load of results for the one above.

would a single view with two displays work any better? Or can I set the default to 'no result' and if so how?

Also, I initially tried the above using 'Exposed Form' setting with 'Input required' and it made the bottom view not work at all. The Exposed form 'Basic' seems to work as you suggest, but I get all the results on page load, and I'd rather have it as showing no results on page load.

any ideas of a way forward for any of these issues?

couturier’s picture

I'd have to agree with #1 - when you have more than one View on a page, the page can be so busy for users, plus it slows down your page load, and that is very bad for SEO. Simplify is sometimes a very good option. I've had to give up lots of features thought I wanted when I first started building my site, and now I'm happy with the simplicity of it, plus I have really fast page loads and great SEO.

xandeadx’s picture

Version: 7.x-3.0-rc1 » 7.x-3.x-dev
Assigned: MStrzelecki_ » Unassigned
Issue summary: View changes
albabosh’s picture

This is really a 'must have' option when it comes to Services Views REST API.