PluginUs.Net - Business Tools for WooCommerce and WordPress

[realize your idea - make your dreams come true]

Support Forum

You need to log-in to create request (topic) to the support

upgraded from WOOF

The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page please
If you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.

Now the search doesn't work.

Is there a rescan/rebuild cache/change shortcode i need to do?

many thanks,

Marcus

Hello Marcus

Please drop  me  exact  link to the  issue

we are running Version 1.3.4.4

Here is a staging link:

https://parrfoundatist.wpengine.com/shop/

It is the search in the blue bar.

Weirdly it was just coming back with no results for a search that should bring lots e.g. PARR

However today it is throwing a 502 error.

 

Hello

For some reason your theme doesn't have the"search" template

Please  drop me  screenshots  of  the  text search  options

 

Hi Pablo,

Missing Search template - yes, we inherited this site. We tried to reactivate the search template but couldn't get it working. This meant most plugins would not give search results.

However WOOF did. So we used that one for ages. When you updated to Husky it stopped working. I am not sure if the method you now use needs a search template whereas before it didn't?

WOOF has stopped working so we have to update now.

many thanks for any pointers so we can get this working again.

 

Try  these  option  to  test - https://share.pluginus.net/image/i20231003125711.png

 

Set as suggested but still get the 502 error.

Ok!  try increasing the timeout on the server - If you have no experience, it is better to contact hosting support

if this happened recently, it may indicate that your server is overloaded

tl;dr:

Hi, It is not the long process killer. This is set to 60 seconds. It errors way before that. Interestingly the AJAX search works. (we don't use that though)

We tested the server (a) to make sure it is not overloaded (we have a dedicated super fast WPE server so i don't think it is a resources issue) and (b) we turned the Long process killer off completely and we still get the same error after 3-5 seconds.

 

 

Here is the transcript:

Hello!! How can I help out today?
Hi Leslie, we are having issue with a search plugin. We used to use WOOF plugin for shop searches. However they have rebranded and I am guessing changed their code.
their search no longer works on the latest version. I have been speaking to their plugin devs and they are saying it is because the server timeout is set to low
the site in question:
Happy to help if I can! Which site is this for?
Thanks!
if you do a search for PARR for example this used to bring back lots of results. It now 502 errors
Thanks for that!
I'm digging in on this now!
great thank you. any help greatly appreciated. we have been not updating the plugin for a year or two but the old plugin no longer works so we will have to deal with the new
It's worth noting that there is a fatal error from the theme, but may not be related: PHP Fatal error: Uncaught Error: Call to undefined function get_field() in /nas/content/live/parrfoundatist/wp-content/themes/mpf/header.php:108
i don't think it is but looking at that now
thank you!
has the error gone now?
Let me check here!
Looks like it! But I do see you're right that it wasn't related.
yeah it still 502s
i am not sure if the plugin dev is right but 502 do occur on timeouts. however i think you guys set at 30 seconds and that error seems a lot quicker than that. *that may not be how it works ;)
I'm not finding anything in the logs for the 502 on our end. It errors pretty quick, so that'll mean it's not getting killed by the long process killer that we have set up. Since timeout isn't the issue, it may be better to reach out and let them know. I can test turning off the Long process killer as well to confirm if you'd like!
the error - it was a bit of script we inherited from the original site designer to set a mobile menu. I have removed it as it that is set elsewhere.
can you, if it is super quick to do. Then i can go back fully armed ;)
Yup yup!
it seemed to take longer to error but still 502s so we are sure it is not a long process error correct?
I'm watching the server here first to make sure we won't cause any trouble disabling that. The long process killer would kick in after 60 seconds or so. But I'm seeing it error after 3-5 seconds-ish.
I'll be a minute here as I confirm we're okay to turn that off.
fair. all seems correct
This are in a good spot so I'm disabling now and testing in a moment here!
great thank you
Of course! It's still disabling here, but I'll let you know once it's finished!
With the LPK off, it's still 502ing for me here. :(
what is interesting is the ajax search pulls the right data back. Ok it is definitely not a timeout error. Can you put that back on and i will get back to the plugin dev
Yup! I've got it toggled back on now!
great thank you for your time have a great day
You too, Marcus! Do let us know if we can help out with anything else there! Cheers!
Leslie

 

Hello

Ok! this is interesting

Can  you  drop me  wp-admin+FTP access - https://share.pluginus.net/image/i20230222134241.png ->https://share.pluginus.net/image/i20230222134615.png - I will  check  it

It says I have saved the hidden data so you should have access to both.

 

many thanks

Hello

Please  do a test

I  added  in  functions.php:

add_filter('woof_husky_query_post__in', function($do){
return false;
});

This works perfectly in staging but just tested on live and cleared cache at server and cloudflare level and it doesn't seem to work there?

I have replicated the settings for search that you set in the first place. Is there another step other than adding the code above to functions?

martinparrfoundation. org

Hello

no, the main change that fixes this is the code in functions.php

Perhaps you added the code to the wrong theme or to the block with conditions

Please  drop me  screenshots of  the  code

I added a comment above so I knew what it did.

I then downloaded the functions.php from the staging and added to live.

There are only two themes in the folder. An unused child theme and the last devs main theme.

I am certain it is in the right theme. (you can view it in Appearance/Theme Editor).

So I don't think it is that.

I have cleared cache at WPEngine and Cloudflare and my browser so I don't think it is that (WPE cache heavily)

I am thinking maybe the page needs to be excluded from their cache maybe?

Not sure what conditions could be set differently, maybe a i have missed a diffeerent setting on the plugin but it all looks identical to me

It does seem odd it works on staging but not live

 

Hello

Ok!  Try   in file - \wp-content\plugins\woocommerce-products-filter\ext\by_text\index.php - change  this  line - https://share.pluginus.net/image/i20231009121845.png

$this->use_post__in = false;//apply_filters('woof_husky_query_post__in', true);

and  do a test

Hey Pablo,

Many thanks, that fixes the 502 on live!

You have made me very happy!

 

Updating in the future

Is this a bug in this version (for some set ups) and will be fixed in the next version?

Or should I note this addition and apply to all future updates? (Also does this live fix require only this line change or does it also need the functions.php line we added as well?)

Many thanks for your diligent work on this.

 

 

This is not a bug, this is a conflict with some settings or third-party code.  Therefore, you should update this code after each plugin update

you can remove the code in functions.php

 

Bad phrasing, apologies.

Cool will turn the filters off for our set up using the file change only.

 

many thanks again for your time on this.

Welcome;)