Forum Replies Created
-
Posts
-
I think there might be missing a query separator, the “?” sign. When I do it like this on my local server:
/#search/?q={phrase}Then it seems to work correctly. This should do the trick.
Great 🙂
If you have an automatic deployment script then that should take care of that automatically. Otherwise I would rather recommend manual setup instead – the staging/live URLs may differ and if any data is stored in reference to the staging site, that may not be correctly transfered.
I’m seeing a completely different list: https://i.imgur.com/4bMChZg.png
Can you please try clearing the browser and site cache (if any). My guess is the browser cache, it may not register the change yet.I quickly logged in to check, and the override was still not enabled. After I turned it ON, the excluded results are no longer present, so it should be okay now. Can you please confirm?
You can choose both, but usually the one without the underscore is the actual ACF field:
passer_til
I would suggest using both, it shouldn’t make any difference.Hi,
Thank you for the details!
I see the issue immediately, Ajax Search Lite is still enabled – please turn off the Lite version, in some cases there are conflicts when the same modules are enqueued twice. The two plugins are separate but share some modules with different versions and that can cause minor issues like this.
Hi,
Thank you very much for the details, this helped me a lot. So you got it correctly, this is the option to exclude the pages.
I am guessing that you are likely using the search to redirect to the results page, in that case make sure the search override was not disabled, so it is turned ON. That should very likely resolve the problem immediately.Hi Will,
You can adjust that URL via these settings: https://documentation.ajaxsearchpro.com/behavior/return-key-and-magnifier-icon-click-actions
