This makes me think there might be publication status inheritance issues at play - for example, a series-level record set to Draft, but a child file-level description that is published. I would check the related archival unit for any such issues, and/or reset the publication status at the top level, so it will inherit down the entire hierarchy.
Similarly, if you have any custom user or group view permissions in place, especially for the anonymous user group (i.e. public users), then it's possible these are configured in some way that could cause a conflict - though this seems like a less likely option to me.
Another possibility is that the nested set has become corrupt. We use a
Nested set model to help maintain hierarchical relationships in the relatively flat, table-based structure of a relational database. Sometimes when long-running operations time out before completing, the nested set can become corrupt. There's a command-line task you can to rebuild this - see:
Does this particular record have a lot of descendants nested below it? If yes, how many? It's possible if this is a very large number, that available memory is being exhausted before the tree fully loads. Check your
webserver error logs to see if there's any additional information, and/or try repeating the action after enabling Debug mode:
Additionally, what is your setting for the Items Per Page in the full-width treeview settings? Does anything change if you try increasing this value (up to a max of 10,000)? See:
Finally, it can always help to ensure that you're not viewing a cached version of a page that may no longer be up to date. You can try clearing the application cache and restarting PHP-FPM before retesting - see:
Don't forget that your web browser also has its own cache - try clearing this as well, or else testing in an incognito / private browser window, where the browser cache is typically disabled by default.
Let us know how it goes, and what you find!
@accesstomemoryhe / him