Mobilecat suddenly returning 0 results. Anyone had this before?

[Tyler Mobley]

So the VM I keep the mobilecat site on was moved to a new host and had updates run recently, but all in all everything should be the same on the server. However, mobilecat now just responds with "0 results" for any search. I'm not seeing any errors in firebug, but the response just comes back blank. Has anyone ever seen behavior like this? The briefcit details are still visible in catalog result source, so the results its looking for should be there. Any ideas?

[anna headley]

I've never seen this. Time for some print debugging?

On Thu, Jan 9, 2014 at 11:57 AM, Tyler Mobley <mobl...@gmail.com> wrote:

So the VM I keep the mobilecat site on was moved to a new host and had updates run recently, but all in all everything should be the same on the server. However, mobilecat now just responds with "0 results" for any search. I'm not seeing any errors in firebug, but the response just comes back blank. Has anyone ever seen behavior like this? The briefcit details are still visible in catalog result source, so the results its looking for should be there. Any ideas?

--
You received this message because you are subscribed to the Google Groups "mobilecat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobilecat+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Tyler Mobley]

Yep, I'm digging around now. Trying to see if the problem is app-side or catalog-side. 

Am I correct in assuming the GET request going to our catalog is along the lines of:

http://catalog_url/search/?searchtype=X&searchscope=0&searcharg=<query>

? I'm not super familiar with simple_html_dom, but I'd like to see the actual query mobilecat is sending to see if the catalog itself isn't accepting the query. I can see the AJAX response and response/request headers but I'm not sure how to get to the actual request content. Thrilling start to the new year!

[Tyler Mobley]

Looking around there's definitely just an Apache/PHP issue lurking somewhere on the server. Not a mobilecat problem directly, so off I go. 

[anna headley]

Good luck!