Search still works, but the custom path no longer seems to send the info to the external site. It just refreshes the same page (and clears the block) or loads the home page (if it's set to open results in a new window). It was working fine for months. I did some module and core updates last night (now on 7.22), but have no other search specific modules installed. I don't see any errors and nothing in the logs. When I go directly to the desired external search page (the path I've entered into custom search paths), it loads fine (not a problem with the external site loading/working on its own).

Any thoughts on where else I can look/test to get this working again? Any other modules (and their updates) that might have affected this?

I've cleared the cache, run update.php, manually cleared the cache tables, run cron, turned off jquery update... I also put the old custom search files back on the site to see if that did it and it did not (so this might not be a 7.12 specific issue -- might happen with previous versions, as well).

If you want to look, it's http://geothermaldata.org -- search in the upper right or on the search page. It's the "data" search that goes externally (to a subdomain hosted elsewhere).

Thanks for any thoughts. Until this last round of updates, the search worked flawlessly.

Comments

jdanthinne’s picture

Status: Active » Postponed (maintainer needs more info)

I just did a clean install of Drupal 7.22 + Custom Search 7.12, and configured search box like yours, and everything is fine. When I choose "Data", it redirects me to http://search.geothermaldata.org#mysearch.
Hard to tell from my side what's wrong in your install without having access to the backend. Try perhaps to do a local copy of your site, and disabling other modules to see which one is causing trouble…

pjbarry21’s picture

Well, it gets more interesting. Not only did disabling the modules not get it to work (no change or the site just didn't load when I disabled each module on its own), a rollback to the previous version of the site (pre-updates to core and a handful of modules) shows that it didn't work then, either (was just not reported to me until recently). So the issue goes further back than I originally thought. I don't have a ton of time to debug right now and not sure what to check next (I've got a workaround up on the site), but if anything comes to mind (something for me to check or a known conflict comes to light) or anyone else runs into this and would like to share, I'd appreciate it.

Thanks.

jdanthinne’s picture

Do you use a base theme with overrides?

pjbarry21’s picture

We're using TB Sirate -- based on Nucleus. And we didn't do much to customize it (it was a site that had to go up fast). We're still using the betas we used when we first created the site -- haven't updated to the latest stable release for either (haven't had the time, but may have some time in a week or so to do the updates to the themes).