[Resolved] Custom search (filters) don’t work with AJAX after plugin update

[Author]

Posts

[Matthias Wagner]

Hi support team,

Background: I had trouble of updating the toolset plugins via Plugins/Commercial ("Activating..." at the types plugin never ended, site showed "Critical error", renamed types directory and installed it via download). I updated all other used plugins as well.

The site is running again, but since then all custom search filter do not work. Example: hidden link
Once a item is selected the result area reloads, but shows wrong results. Also the search form disappears.

Additional info: after such a search the URL is:
hidden link
If the last two parameters are taken away (&wpv_aux_current_post_id=3551&wpv_view_count=3554), so only:
hidden link
the search form appears again and the correct results are shown.

Thanks for any help!

Best,
Matthias

[Christian Cox]

Hi, I'll be glad to help figure this out. Can we try these basic troubleshooting steps first?
- Temporarily activate a default theme like Twenty Twenty One
- Temporarily deactivate all plugins except Types, Views and Layouts (and maybe a Maintenance Mode plugin if you'd like to activate Maintenance mode during testing)
- Temporarily deactivate any custom code snippets in Toolset > Settings > Custom Code tab
- Temporarily comment out any custom JavaScript added in this View's JS editor panels
- Test again
- If the problem is resolved, reactivate inactive components one by one until the problem returns
- If the problem is not resolved, I may need to take a closer look in wp-admin. Can you provide login credentials here in the private reply fields?

[Christian Cox]

I set up a test system and found out that a plugin called "WordPress Login form" (https://wordpress.org/plugins/wp-login-form/) causes this issue. Unfortunately we use this plugin frequently. So, how to proceed?
Okay let me try installing this plugin on my own test site to see if I can replicate the issue in a similar setup. If not, I may need to make a clone of your site so our team can investigate the conflict in more detail. Please stand by and let me run some tests on my own environment, and I'll give you an update shortly.

[Christian Cox]

Okay after running some tests in my local environment, I have been able to successfully reproduce the problem in a specific scenario. The View must be "split" so to speak, where the filters and results are displayed separately either by separate shortcodes or by separate View blocks in a Layout. If I place the same View using one shortcode or one View block in a Layout, the problem does not seem to occur.

I'm asking my 2nd tier support team to investigate this compatibility issue and find out if there's anything we can do on our end to fix this conflict.

Until we get some feedback, the best workaround I can think of is to insert the View in your Layout using a single full-width View block that includes both the filters and the results. To display the filters and the results in a 1/3 - 2/3 columns-based design, you can use the View's Output Editor section to create a column-based layout with Bootstrap 3 classes like so:

<div class="container">
  <div class="col-sm-4">
  [wpv-filter-meta-html]
  </div>
<div class="col-sm-8">
  [wpv-layout-meta-html]
</div>
</div>

[Matthias Wagner]

Hi Christian,

thanks and a real great support!

The work-around help only "half way": the form now stays on the page, but the results are still wrong.

But anyhow: I realized that also other AJAX functions like the pagination don't work. So, we need another solution anyhow.

That said, I will wait and see if your team can solve this conflict.

Thanks again!
Matthias

[Christian Cox]

Okay thanks for the clarification, I overlooked this part of the problem in my initial analysis. I've updated my 2nd tier support team so they are aware that the filters are not applied correctly when the plugin is active, regardless of whether the View is split or not. I'll keep you updated as I receive additional information. Right now our team is still investigating. One recommendation is to use the Views login form shortcode instead of a 3rd-party plugin, but I'm not sure if you can accomplish everything you need with the Views login form as opposed to the login form plugin.

[Matthias Wagner]

Thanks for letting me know, Christian!

I'll take a look at [wpv-login-form]! (OMG, I didn't even know that there is such a shortcode oo- )

Regarding your 2nd tier support investigations: I'll stay tuned.

Thanks,
Matthias

[Christian Cox]

Hi, we contacted the plugin's author and explained the issue. They just released an update for the plugin that seems to resolve the problem in our local testing. From the author: "I can see what is happening. It was a mistake on my part. I have just released an update to fix this. Let me know if it resolves the issue."

[Matthias Wagner]

My issue is resolved now. Perfect! Thanks for the great support!