We've been using this module for a very long time, but needed to change the location of our Google Search Utility from one used just by our agency to one shared by all agencies. As a fake example, imagine that our Google Search Appliance Host Name used to be "http://search.agency.gov" and now it's located at "http://search.state.gov". I've checked several times and the GSA Host Name has definitely been changed.

Now, also imagine many of the URLs of our agency's site have changed since the switch-over. So, let's say one piece of content was named "http://agency.gov/myAwesomePage", but was changed to "http://agency.gov/myGroovyPage" while the change-over to the new search box was happening.

Since we have a new search box, it should have indexed the site and should return "myGroovyPage", but it's still finding "myAwesomePage" instead. I've tried running cron and clearing caches several times to no avail. I know for a FACT that these are old search results and it is a completely new server. It shouldn't be returning any old content; it should be a fresh index. Somehow these results are being cached in Drupal, but don't get cached when the site caches are cleared on the /admin/config/development/performance page.

Does anyone know how to clear all the search caches? Or is something else going on?

Thanks
=Adam=

Comments

iamEAP’s picture

That's definitely odd, Adam. If you query the GSA instance directly (e.g. at search.state.gov directly, as opposed to through Drupal via this module), do you see the same results? That would indicate that there's an issue with your crawl settings, or some other issue with indexing.

This module doesn't cache results in any way, other than through the Drupal page cache (which would be cleared via the mechanism you described above).

loopy1492’s picture

Status: Active » Closed (works as designed)

Oh my gosh. They used the wrong URL for the crawl. I'm not used to relying on others to do stuff for me. I should have checked that.

Thanks so much. That was a great troubleshooting tip.