Bug #13124

Full-width treeview paging button not shown for public users

Added by Dan Gillean 3 months ago. Updated 2 months ago.

Status:VerifiedStart date:07/26/2019
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Treeview
Target version:Release 2.5.2
Google Code Legacy ID: Tested version:2.5
Sponsored:No Requires documentation:

Description

In Feature #12611, we added paging to the full-width treeview when there were more than 50 immediate child records from the top-level parent. This was intended to help improve load time performance for large collections. However, currently it is not working as expected for public users.

To reproduce

  • Find, import, or create a large collection, with many (100+) immediate children. I'm attaching a CSV with an example record that can be used to reproduce.
  • In Admin > Settings > Treeview, make sure the treeview is set to full-width
  • Make sure the large collection is published
  • While logged in, navigate to the description. Note the Load button visible in the top-right above the treeview.
  • Log out, and return to the collection

Resulting error

  • No load button is shown in the public view
  • Only the first 50 child records are shown in the treeview

Expected result

  • Feature behaves the same regardless of publication status
  • Load button is available to public users

large-items-collection.csv Magnifier (383 KB) Dan Gillean, 07/26/2019 01:42 PM


Related issues

Related to Access to Memory (AtoM) - Feature #12611: Add paging to full-width treeview for top-level records w... Verified 12/03/2018

History

#1 Updated by Dan Gillean 3 months ago

  • Related to Feature #12611: Add paging to full-width treeview for top-level records with more than 50 immediate children, to improve performance added

#2 Updated by Mike Cantelon 3 months ago

  • Status changed from New to Code Review
  • Assignee deleted (Mike Cantelon)

#3 Updated by Mike Cantelon 3 months ago

  • Status changed from Code Review to QA/Review

Merged into qa/2.6.x.

#4 Updated by Mike Cantelon 3 months ago

  • Status changed from QA/Review to Code Review

Found related issue.

PR for CR: https://github.com/artefactual/atom/pull/942

#5 Updated by Mike Cantelon 3 months ago

  • Status changed from Code Review to QA/Review

Merged into qa/2.6.x.

#7 Updated by Dan Gillean 2 months ago

  • Status changed from QA/Review to In progress
  • Assignee set to Mike Cantelon

Mike do you want to go ahead and backport this to stable/2.5.x when you have time, so we don't forget to do it later?

#8 Updated by Mike Cantelon 2 months ago

  • Status changed from In progress to QA/Review
  • Assignee changed from Mike Cantelon to Dan Gillean

Good thinking. I've backported the two fixed to 2.5.x.

#9 Updated by Dan Gillean 2 months ago

  • Status changed from QA/Review to Feedback
  • Assignee changed from Dan Gillean to Mike Cantelon

Hey Mike, just tested on stable/2.5.x and it's not working there. I looked at the branch's commit history and didn't see it added?

#10 Updated by Mike Cantelon 2 months ago

  • Status changed from Feedback to QA/Review
  • Assignee changed from Mike Cantelon to Dan Gillean

#11 Updated by Dan Gillean 2 months ago

  • Status changed from QA/Review to Verified
  • Assignee deleted (Dan Gillean)

Also available in: Atom PDF