Home › Forums › Product Support Forums › Ajax Search Pro for WordPress Support › Conflict with Encyclopedia Pro Plugin?
- This topic has 6 replies, 2 voices, and was last updated 3 years, 5 months ago by
Ernest Marcinko.
-
AuthorPosts
-
December 19, 2022 at 9:41 pm #40575
dekerio
ParticipantHello WordPressDreams,
we just bought your pluginAjax Search Pro.
Everything works fine but the search results page doesn´t show due to an conflict with this plugin:
https://dennishoppe.de/en/wordpress-plugins/encyclopediaKinsta log gives us this snippet:
2022/12/19 15:33:37 [error] 43213#43213: *126865 FastCGI sent in stderr: “PHP message: PHP Warning: foreach() argument must be of type array|object, string given in /www/clone2btde_741/public/wp-content/plugins/acf-cpt-options-pages/class.acf-cpt-options-pages.php on line 32PHP message: PHP Fatal error: Uncaught TypeError: WordPress\Plugin\Encyclopedia\Core::checkSearchRequestForExactMatch(): Argument #1 ($posts) must be of type array, null given, called in /www/clone2btde_741/public/wp-includes/class-wp-hook.php on line 308 and defined in /www/clone2btde_741/public/wp-content/plugins/encyclopedia-pro/includes/core.php:62
Stack trace:
#0 /www/clone2btde_741/public/wp-includes/class-wp-hook.php(308): WordPress\Plugin\Encyclopedia\Core::checkSearchRequestForExactMatch(NULL, Object(WP_Query))
#1 /www/clone2btde_741/public/wp-includes/plugin.php(256): WP_Hook->apply_filters(NULL, Array)
#2 /www/clone2btde_741/public/wp-includes/class-wp-query.php(3304): apply_filters_ref_array(‘posts_results’, Array)
#3 /www/clone2btde_741/public/wp-includes/class-wp-query.php(3749): WP_Query->get_posts()
#4 /www/clone2btde_741/public/wp-includes/class-wp.php(663): WP_Query->query(Array)
#5 /www/clone2btde_741/public/wp-includes/class-wp.php(783): WP->query_posts()
#6 /www/clone2btde_74” while reading response header from upstream, client: 2a02:908:d85:d900:61c2:e1b7:19e5:c51b, server: clone2btde.kinsta.cloud, request: “GET /?s=test&asl_active=1&p_asid=1&p_asl_data=1&customset[]=com_roboadvisor&customset[]=com_bank&customset[]=com_insurance&customset[]=com_trademarket&customset[]=ser_online_broker&customset[]=com_finance_portal&customset[]=ser_cfd_broker&customset[]=com_broker&customset[]=ser_daytrade_broker&customset[]=ser_futures_broker&customset[]=ser_trademarket&customset[]=ser_tradingplatforms&customset[]=ser_etcs&customset[]=trading_webinar&customset[]=encyclopedia&customset[]=com_trustee&customset[]=ser_forex_broker&customset[]=page&customset[]=post&asl_gen[]=excerpt&asl_gen[]=content&asl_gen[]=title&qtranslate_lang=0&filteUnfortunately we have more then 2,000 definitions in this glossary which of course should all be searchable.
Can you help us with this problem?
Thanks, DavidDecember 20, 2022 at 3:34 pm #40592Ernest Marcinko
KeymasterHi David,
In the error messages there is no mention of our plugin. I suspect that the other plugin tries to do something with the search results, but the function hooked to the results array bugs out for some reason.
First, can you please switch to the Ajax Search Pro version, and uninstall the Lite version, to see if that changes anything.
December 20, 2022 at 4:22 pm #40599dekerio
ParticipantYou cannot access this content.
December 20, 2022 at 4:39 pm #40601Ernest Marcinko
KeymasterHi David,
I see you have some custom CSS applied for the lite version, that makes the differences. You will have to change the CSS rules to accomodate the Pro version, the class names and the IDs are a bit different.
Can you try to turn off the search override feature here? That will remove the search hook from the posts results, so the other plugin can apply it’s hooks.
December 20, 2022 at 5:14 pm #40605dekerio
ParticipantYou cannot access this content.
December 20, 2022 at 5:33 pm #40606dekerio
ParticipantYou cannot access this content.
December 21, 2022 at 2:17 pm #40616Ernest Marcinko
KeymasterOkay, that is great then!
-
AuthorPosts
- You must be logged in to reply to this topic.