Search line does not work

as soon as I enter something in the search in the Festinger Vault plugin nothing happens.

No matter if Elementor, Astra, Yoast or others it just stays without searching anything.

Can it be because of the PHP version or is there another problem?

Search still a solution

Thanks for reporting this @damarketing.

Could you try to flush your browser cache and disable ‘plugin caching’ from your account’s dashboard?

tried is not working

Same problem. I just installed Festinger plugin, activated it with the license, and tried to search the vault. It’s as if the enter key doesn’t work. There’s no way to initiate the search for the term I typed.

1 Like

Thanks for letting us know @damarketing and @damarketing.

Our technical team is informed about this issue and there will be a solution soon.

Is there any news about this?

Hi @rebber2 and @damarketing,

We checked the issue here.

Could you please check the memory PHP limit of your WordPress instance?

As it looks like your hosting doesn’t allow to run the plugin properly.

max_input_vars = 3000

We informed our technical team again and they will get back to me asap.

Just FYI I also have the same issue. Dedicated VPS

Whenever i try to search something with the FV Plugin i run into the follow exception

4109:1 Uncaught SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
    at JSON.parse (<anonymous>)
    at Object.success (scripts.js?ver=3.8.1:929:25)
    at c (jquery-3.4.1.min.js?ver=3.8.1:2:27742)
    at Object.fireWith [as resolveWith] (jquery-3.4.1.min.js?ver=3.8.1:2:28487)
    at l (jquery-3.4.1.min.js?ver=3.8.1:2:78789)
    at XMLHttpRequest.<anonymous> (jquery-3.4.1.min.js?ver=3.8.1:2:81117)

Which is caused by an SQL Exception:

SQLSTATE[23000]: Integrity constraint violation: 1052 Column &#039;title&#039; in where clause is ambiguous (Connection: mysql, SQL: select jreviews_data.title, jreviews_data.image, jreviews_data.support_link, jreviews_data.summary, jreviews_data.featured, jreviews_data.hits, jreviews_data.href, jreviews_data.modified, jreviews_data.preview, jreviews_data.type_slug, jreviews_data.unique_rand_md5, jreviews_data.version, jreviews_data.type_slug, jreviews_data.category_slug, jreviews_data_meta.verified_slug as new_generated_slug, IF (jreviews_data_meta.verified_slug IS NULL, generated_slug, jreviews_data_meta.verified_slug) as new_generated_slug from `jreviews_data` left join `jreviews_data_meta` on `jreviews_data`.`id` = `jreviews_data_meta`.`jreviews_id` where `jreviews_data`.`title` !=  and `title` like TEST order by `hits` desc)

Thanks for your reports @grahammiranda13 and @easkieni.

Our technical team is informed and a solution will be provided very soon.

some news here?

1 Like

It’s weekend @damarketing, we do, as programmers, sleep and enjoy some time off as well.

We checked the issue here for both members @here.

The reason we found this is that we’re sending quite a big data to your server and we are saving that inside the database. If searching from the cache is disabled, it still downloads the JSON data from our website engine. The issue is that the data is failing as the server/php/cache/nginx fails to process the big data to filter the search.

We are trying to see if the search can be triggered directly from our engine for the website which has an issue with this. So for now, we don’t have an instant solution, but we will do our upper best after the release of our new features to fix this issue as well.

Here is what my Server Log shows up:	500	POST /wp-admin/admin-ajax.php HTTP/2.0	Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36 Edg/112.0.1722.39	197	SSL/TLS-Zugriff für nginx
21178#0: *1460925 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught TypeError: array_filter(): Argument #1 ($array) must be of type array, null given in /var/www/vhosts/
Stack trace:
#0 /var/www/vhosts/ array_filter()
#1 /var/www/vhosts/ fv_search_ajax_data()
#2 /var/www/vhosts/ WP_Hook->apply_filters()
#3 /var/www/vhosts/ WP_Hook->do_action()
#4 /var/www/vhosts/ do_action()
#5 {main}
thrown in /var/www/vhosts/ on line 822" while reading response header from upstream

Just for info, I get this error on different servers and different installation :wink:

Thanks for getting back to us!

We forwarded your error to our technical team in order to fix the issue.

And something I have forgotten, just before the latest update, i had to increase the MySQL max_allowed_packet value to 1GB to make your plugin working. Maybe this hint will help as well.