Forum Replies Created
-
Posts
-
Hi!
I’m afraid that is not possible – the archive page automatically limits that. The fruits archive page is bound to that very category, so the search is automatically limited to that.
Even if I tried to somehow “hack” the non-archive items there, the final loop would simply remove them either way.Hi,
The search should be okay – but the category filtering on the category page might be a problem here. See you try to filter the items in the “Faq” category page to switch to a different category from the same taxonomy. But because this is a specific taxonomy term (Faq) archive page, it’s not possible to simply change it to another one, as that is a different archive alltogether. An archive page for a category should always display items matching that category – because that is what it’s made for.
This could very likely work on the post type archive page though – so showing everything from that post type then filtering by taxonomy or vice versa.
Another possibility is to not use the archive for that, but simply use the plugin on a separate single page, preset the filter to the “Faq” item, then enable the auto populate. That way it will automatically show the items for that FAQ in the search results container, and the user can switch to a different categor – like this example.
Hi,
You could try the compact box layout and place the plugin as a menu element. If your theme supports widgets/modules on the header, that is even better, I recommend placing the plugin shortcode there.
As for the compact box layout configuration, try something like this.
Hi,
The results page is controlled by your theme, the plugin can’t affect that. Try looking at your theme options, usually modern themes have options to make changes to the archive pages, such as the results page.
The plugin author should make sure not to load it’s script on other plugin pages – that is a very bad practice, sometimes developers forget to check that. From Ajax Search Pro perspective we can’t really do anything to prevent that, as it addresses very generic selectors.
I suggest contacting their support to make sure they fix that, as many other plugins also use the same sortable feature (page builders etc..) and may cause further issues, which you may not even notice.
Thank you, I see it now.
The issue is caused by this plugin. It loads up a script file on the Ajax Search Pro back-end and overrides the drag/drop UI field behavior on accident. The cause of the issue is this file. It should not be loaded on the plugin back-end, or they should rather use more specific DOM selectors to avoid the conflicts.
Turning off that plugin temporarily will resolve the issue.Hi!
Thank you for all the details it helps us a lot.
To create and get to know the filters, I recommend looking at this documentation. You will find sections there fo all types of filters you may need 🙂
