Search is Broken

[grahamd711Participant]

After pushing from our staging to production site, the search function has stopped working.

We also changed a few DNS settings so my assumption is that the file paths are just not working. I deactivated and reactivated the plugin and it does not seem to be working.

My console logs are showing a 500 server error.

Here is the full log:

 POST http://liveintent.com/wp-admin/admin-ajax.php 500 (Internal Server Error)jquery.ajaxsearchpro.min.js?ver=4.1:2 sendjquery.ajaxsearchpro.min.js?ver=4.1:2 m.extend.ajaxjquery.ajaxsearchpro.min.js?ver=4.1:2 m.(anonymous function)jquery.ajaxsearchpro.min.js?ver=4.1:76 methods.searchjquery.ajaxsearchpro.min.js?ver=4.1:76 (anonymous function)jquery.ajaxsearchpro.min.js?ver=4.1:2 m.event.dispatchjquery.ajaxsearchpro.min.js?ver=4.1:2 r.handlejquery.ajaxsearchpro.min.js?ver=4.1:2 m.event.triggerjquery.ajaxsearchpro.min.js?ver=4.1:2 (anonymous function)jquery.ajaxsearchpro.min.js?ver=4.1:2 m.extend.eachjquery.ajaxsearchpro.min.js?ver=4.1:2 m.fn.m.eachjquery.ajaxsearchpro.min.js?ver=4.1:2 m.fn.extend.trigger(index):1363 (anonymous function)jquery.ajaxsearchpro.min.js?ver=4.1:2 m.event.dispatchjquery.ajaxsearchpro.min.js?ver=4.1:2 r.handle
j

I also purged the cache to see if that would work. Any ideas on how to get this back up and working?

• This topic was modified 9 years, 7 months ago by  grahamd711.

[Ernest MarcinkoKeymaster]

Hi!

The error message suggests that there is no ajax response due to a fatal error somewhere along the way. Turning on the error reporting in the wp-config.php might print something into the request.

As long as the wordpress paths are correct the search paths should be correct as well. You haven’t changed the domain, so everything should be ok.
Try to open op every settings page from the ajax search pro submenu and save them again. Maybe some of the options were lost along the way – I would say most likely the caching options.
Also deactivating/activating the plugin sometimes helps.

If nothing helps you can provide temporary ftp and amdin access and I can try to debug through the ajax handler to see where the error comes from.

Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)

[grahamd711Participant]

Thank you for the quick reply!

I did try a the above methods and it is still not working. I do want to mention that I changed the domain as we went live on WPEngine hosting.

Old: http://www.liveintent.wpengine.com
New: http://www.liveintent.com

I don’t know if that would have any effect. Since the staging url http://www.liveintent.staging.wpengine.com remained the same (and the search still works)..I assume it is an issue with the domain possibly changing file paths somewhere along the way.

Any other ideas before I can send over admin creds? This is a production site so it is a bit concerning to be editing and testing lots of things while on the live site.

Below is some more error logs:

[Tue Feb 10 21:12:03 2015] [error] [client 38.88.218.190] PHP Fatal error: require_once() [function.require]: Failed opening required ‘/nas/wp/www/cluster-2209/liveintent/wp-content/plugins/ajax-search-pro//includes/imagecache.class.php’ (include_path=’.:/usr/share/php:/usr/share/pear’) in /nas/wp/www/cluster-2209/liveintent/wp-content/plugins/ajax-search-pro/search.php on line 11, referer: http://liveintent.com/

I went to line 11 in search.php to find the below line…

require_once(ASP_PATH.”/includes/imagecache.class.php”);

Looks like the error is being thrown because it cannot find the imagecache.class.php file?

[Ernest MarcinkoKeymaster]

Yes, it means that file is missing. It probably wasn’t uploaded.

Instead of uploading the ajax search directory, I recommend rather deactivating and deleting the plugin, then uploading it again. The settings table and the options will remain there. That should solve the problem instantly. You should save the settings again once uploaded, just to make sure that everything is consistent.

Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)

[grahamd711Participant]

Works now!

For future reference, if anyone is using WPEngine for their WordPress hosting… and has this issue. You need do delete the plugin on both staging and production. Then install on production first, followed by staging. Assuming something was goofed when I deployed from staging –> production multiple times yesterday.

Seems backwards but this was the only way I got it to work! Thanks for the help and super quick response, love the plugin.

[Author]

Posts