You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, opening a record/material of a large repository/series does not focusm set the focus of the full-width treeview on the current record/material.
Expected Behavior
Regardless of the size of repository/series, when you open a record/material, the treeview should always focus on the current record/matieral.
The text was updated successfully, but these errors were encountered:
melaniekung
added
the
Type: bug
A flaw in the code that causes the software to produce an incorrect or unexpected result.
label
Jun 12, 2024
@melaniekung if you are seeing this in older installations it may already be solved by #1748 - typically when we see this behavior in the past, it was due to a child record being outside the initial paging value set for the full-width treeview. PR #1757 increased the default installation value to 8000 which should most issues (if this is in fact the cause) save for the largest of hierarchies - however, I don't know if there was a migration script for upgrading users, and even if there was, I doubt it would modify the existing value if a user had already modified it themselves.
Therefore, for any existing installation where this behavior is seen, my first suggestion would be to check the treeview pager value and try increasing it, restarting services / possibly reindexing, and then see if you can reproduce the problem.
If yes: then it's likely something else. If no, then it may be a solved issue!
Current Behavior
Sometimes, opening a record/material of a large repository/series does not focusm set the focus of the full-width treeview on the current record/material.
Expected Behavior
Regardless of the size of repository/series, when you open a record/material, the treeview should always focus on the current record/matieral.
The text was updated successfully, but these errors were encountered: