Hi sbailey4,
Can you upgrade the plugin for about 30 minutes to allow us to take a look at the issue.
Thanks,
Igor
Yes its been updated to 1.4.13 and the url is http://staging.ahdpg.com The live site with version 1.4.12 is http://www.ahdpg.com
-
This reply was modified 7 years, 4 months ago by sbailey4.
Great. I’ll check it now and let you know what the results.
Thanks,
Igor
Hi sbailey4,
I’ve found the reason. The settings are related to the live site. So the search page URL in settings set to http://www.ahdpg.com/search/. So it will not work on http://staging.ahdpg.com/search/. To fix it you just need to re-save the settings on the searchIQ -> Options tab.
Let me know if it will not work for you.
Thanks,
Igor
Also create new search engine for staging site because if you change the settings on staging it will affect on the live site as well. To create new search engine you just need to reset the settings on the Configuration tab and create the engine from the first step.
Thanks,
Igor
I will give that a try. However I already have 2 search engines setup. One for each site. Both work on 1.4.12. So could it be that I only updated the staging site and not the live site to the latest version? I typically use staging.x.x to make sure plugins dont break anything and once all is well THEN I update the live site. Certainly I can try and update both to the latest if need be since I can go back if I have to. Thanks for the info!
Hi sbailey4,
For now I can see in our system that both sites using the same engine from live site. I think you have copied database from live site to staging. Also I can see you already have created search engine for staging site. If you reset the settings and pass all the steps from the first one. It will work fine and will not conflict with live site.
By the way, I’ve forgot that we have protection for similar cases. And if you created search engine on site A then you cannot change settings or anything else from different site (for example, from site B)
Thanks,
Igor
I think I am good. Came to reply that I did in fact copy live database to staging some weeks ago due to another issue so I reset config totally and re-applied API key on staging and that seems to have solved it. I see you came to the same conclusion regarding the database (good find). Interesting the issue didn’t appear until I updated staging site plugin version. Anyway I think I am good. Thanks for the quick response! Appreciate your time and help!