Bug #5638

settings for default browse order not being applied

Added by Tim Hutchinson over 8 years ago. Updated over 8 years ago.

Status:VerifiedStart date:09/21/2013
Priority:HighDue date:
Assignee:José Raddaoui Marín% Done:

100%

Category:Administration / settings
Target version:Release 2.0.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

(testing with 2.0.0 - 102)

The default sort order for applicable browse pages is:
- descriptions - last updated
- names - last updated
- institutions - alphabetical
But these defaults override the "sort browser" settings.

To reproduce:
- log in as an administrator
- under global settings, set Sort browser (users) to last updated and Sort browser (anonymous) to alphabetical
- stay logged in
- go to browse institutions; default order is alphabetical, but should be most recent
- log out, or open a different browser (so that you are proceeding as an anonymous user)
- go to browse descriptions; default order is most recent, but should be alphabetical
- go to browse name; default order is most recent, but should be alphabetical
- Now log back in
- change the settings to Sort browser (users): alphabetical; Sort browser (anonymous): last updated
- stay logged in
- go to browse descriptions; default order is most recent, but should be alphabetical
- go to browse name; default order is most recent, but should be alphabetical
- now log out, or open different browser (so that you are proceeding as an anonymous user)
- go to browse institutions; default order is alphabetical, but should be most recent

See issues #3881 and #4183 - functional in 1.3.1


Related issues

Related to Access to Memory (AtoM) - Bug #5442: Port "Sort browser" functionality over to AtoM 2.0 Admin... Duplicate 08/07/2013

History

#1 Updated by Dan Gillean over 8 years ago

  • Category set to Administration / settings
  • Assignee set to Jesús García Crespo
  • Priority changed from Medium to High
  • Target version set to Release 2.0.0

Hi Tim,

Thanks for this. This ticket actually duplicates one I filed earlier (#5442) as this is a known task for the developers (I had added an issue ticket as a reminder) - but since you've added much more detailed testing notes to this one, I've marked my original issue as the duplicate and assigned this one.

#2 Updated by Tim Hutchinson over 8 years ago

Great. I'm still feeling my way around searching for known issues.

#3 Updated by Jesús García Crespo over 8 years ago

  • Assignee changed from Jesús García Crespo to José Raddaoui Marín

#4 Updated by José Raddaoui Marín over 8 years ago

  • Status changed from New to In progress

#5 Updated by José Raddaoui Marín over 8 years ago

  • Status changed from In progress to QA/Review
  • % Done changed from 0 to 100

Applied in changeset atom|commit:1b806fc3bb341110e1548f5d29bd04c6b76da251.

#6 Updated by Jessica Bushey over 8 years ago

  • Status changed from QA/Review to Verified

went through full testing in different browsers and as public and admin. all changes worked, database responded accurately to admin settings.

Also available in: Atom PDF