filter (instead of search) custom post type

Home Forums Product Support Forums Ajax Search Pro for WordPress Support filter (instead of search) custom post type

This topic contains 1 reply, has 2 voices, and was last updated by Ernest Marcinko Ernest Marcinko 1 year, 2 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #41988


    On our website we use a custom post type to handle events. To get them displayed properly fitting to the design, we created custom templates/loops.
    There are not really many events, and all are categorized in a few categories.

    Now we want to add a filter option to display only the events from specific categories, using some kind of live/ajax filtering.

    The whole website can stay untouched. For testing, we created a new subpage:

    In there, you can see that the ajax filter using your plugin works in general, but is really slow (we only have a shared webhosting).

    Below the test implementation with your plugin, you can see another test using a different plugin: ->
    That was used just to see if it might work faster in a different way, and that’s the case.

    For us, the big advantage of your plugin is that we can work with the existing templates and loops.
    However, this only brings us an advantage if the functionality is also given, i.e. the filtering works faster.

    Now the question is: Is there a possibility with your plugin not to actually search these custom posts, but only to filter them by category, so that the process is faster?

    Ernest Marcinko
    Ernest Marcinko


    Thank you very much for the details!

    The main difference with the two implementations is, that the other plugin actually uses it’s own results container (not actually filtering the Elementor widgets), which is very different.
    If you do the same with Ajax Search Pro, the results will be populated just as fast or even faster. The reason is, that displaying results via an ajax request to the WordPress ajax handler is much faster, as the front-end does not have to be fetched.
    If you want to replicate something similar to the other plugin output, maybe something like this example, then you can use the auto populate feature to initially display results in the original plugin results container – so not connected to an Elementor widget.

    On a different note, I think you may have some issues on the site front-end, it takes over 11 seconds to load any front page. I measured, because this reflects on how fast the plugin can update the elementor widget with the new results, it has to wait for the server to respond. The actual search process takes like 15 milliseconds, while the page loads for over 11 seconds. The server seems to be fine, the back-end works perfectly and responds super fast, there is something on the front-end delaying the loading.

    Ernest Marcinko

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

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.