Advanced Search not showing results.

Skip to first unread message

Atom Fundceri

Nov 21, 2023, 7:59:06 AM11/21/23
to AtoM Users
Good morning. 

I am an archivist using ATOM and suddenly, whenever I choose a fond in Advanced Search, the software isn´t returning any entry. It has been working fine, but this problem just appeared.

If I don´t choose any fond, the software returns all pertinent entries. Is there any way to fix this? Thank you and sorry if I didn´t explain myself correctly.

Dan Gillean

Nov 21, 2023, 9:18:29 AM11/21/23
Hi there, 

Do you mean if you use the "Top-level description" filter in the Advanced search interface to select a fonds, then there are no results returned when you submit this?

If yes, then make sure that you have also toggled the filter to search ALL descriptions, and not just top-level records - otherwise you will only get the fonds-level record returned! 

In the screenshot below, I have set the top-level description filter to search inside a fonds called "Michael Kelly" in our public demo site (square #1). Notice in square #2 below the radio-button toggle for top-level descriptions vs all descriptions, which you should also change if you have not: 


If you are applying other facets and filters, then you may also just not be getting any matching descriptions. If you are searching a fonds that definitely has lower-level descriptions, you can always try clicking the "Reset" button at the bottom of the Advanced search panel first to clear all previous facets and filters, before setting your top-level description filter. 

Another general question: are you logged in when performing this search? If no, are your descriptions published or in draft mode? If they are in draft mode still, then if you are not logged in you will not be able to see them. For more information on publication status and how to change it, see: 

If those suggestions do NOT resolve the issue, then it could be that there is a problem with your search index. The following will require command-line access to the application - if you do not maintain your AtoM site, you can send the following to the person who does. 

Below I will suggest a few common maintenance tasks that tend to resolve many issues in AtoM. Generally, all of the following commands should be run from AtoM's root installation directory (which is typically /usr/share/nginx/atom if you have followed our recommended installation instructions). You will also find links and further information for each of these tasks on the following documentation page: 
The following also assumes you are running a 2.7.x version, and have followed our recommended installation instructions. If not, check the docs for your major version, and make alterations based on your local customizations as needed. 

First, let's make sure the nested set is properly built - this is what manages hierarchical relationships in AtoM's database, so if it gets corrupted or out of sync, it could cause issues with returning descendant description results: 
  • php symfony propel:build-nested-set
It's also a good idea to ensure that all descriptions have a slug (i.e. a permalink - the unique part of the URL) - sometimes if a long-running process is interrupted unexpectedly, some records can be left without slugs, which can cause unexpected issues. We can generate missing slugs with: 
  • php symfony propel:generate-slugs
Let's also clear the application cache and restart PHP-FPM, so we are sure we are seeing the most up-to-date information and not stale cached results: 
  • sudo systemctl restart php7.4-fpm
  • php symfony cc
Finally, you can try re-populating the search index with the following command. Keep in mind that of these suggestions, this command is the only one that can take a while to run (depending on the number of records in the site), and it will temporarily make ALL descriptions unavailable via search and browse, so is ideally best run outside of regular business hours on a production installation: 
  • php symfony search:populate
You can also get more information about the status of your search index with: 
  • php symfony: search:status
This is useful if trying to run the search:populate task returns an error - if so, please share the output of the status task with us, along with anything you find in the webserver error logs related to this issue: 
Hopefully this will get you sorted! Let us know how it goes, and if you are still having issues, please share as much information about your installation (full version number, any changes from the recommended installation instructions, any local customizations you have, any relevant error logs, etc) as you can, so we can provide better suggestions. 


Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
he / him

You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit
Reply all
Reply to author
Message has been deleted
0 new messages