Hi Carolyn,
Rebuilding the nested set was a good idea. A few further suggestions to try, to rule out the easier solutions if nothing else!
Generate slugs
Let's make sure that all records have slugs. There's two ways you could run this task: if run with no options, then it will only add slugs to records that are currently missing them. If you run it with the --delete option added, then it will delete all existing slugs for main entities and then regenerate them. For archival descriptions, it will use your settings for "Generate permalinks from" - by default this is from title, but can be set to reference code or identifier instead.
The second option (with --delete) is more comprehensive and will also help us check some edge cases. However, if you have customized any slugs in your site (for example, using the "Rename" module to change the default slug) then these custom slugs will be lost if you use the --delete option. See:
Clear caches
Let's make sure that this result isn't showing up because it's a cached version of a record that has since been changed, moved, or deleted somehow. There are a few caches to address. First, Symfony has an application cache to clear:
Next, we need to restart PHP-FPM, which also acts as a cache. This command depends on your PHP version - if you are running PHP 7.4 as recommended for release 2.6, the command is:
If your installation is using an additional cache engine like memcached, it's good to clear that as well. The command shouldn't do anything bad if you don't have it installed, so if you're unsure, you can always try:
Finally, don’t forget that your web browser has its own cache - in some cases, if you are not seeing changes take effect, you might want to try clearing your web browser cache, or at least testing in a private or incognito browser window, where the cache is typically disabled by default. Note that, because AtoM is session based, clearing the web browser cache might log you out of the application. Be sure you have saved any work you are doing in the user interface before doing so!
Rebuild search index
It's also possible that somehow the search index got out of date. Let's rebuild it. Keep in mind that this task is best run outside of business hours - it will temporarily make records unavailable in your site as the index is deleted and rebuilt, and if you have a large site, this can take a while to run:
If none of that works, let us know! I have a couple ideas on possible next steps if the above does not resolve the issue.
Best,