is_search problem

Thank you for the so fast asnwer!

As a matter of fact, the product tag and category tags are not taken from the default language and the results are being shown.

The problem is that I modified woocommerce.php with some if is_search() and some if !is_search() functions.

I will add another private comment with links to show you the difference between the languages (I am just the developer not the owner of the site so I don’t want to post links to it here)

I will add links here as I can’t find where to message you as well 🙂
Later I will erase the links once you see them:

Main language (Hebrew):
http://winners-auctions.com/?s=&product_cat=%D7%9E%D7%9B%D7%99%D7%A8%D7%94-%D7%9E%D7%A1%D7%A4%D7%A8-085&product_tag=%D7%9B%D7%AA%D7%95%D7%91%D7%95%D7%AA

English:
http://winners-auctions.com/en/?s=&product_cat=auction-no-085&product_tag=ketubot

Here I am showing you the same category and same tag filtered in the corresponding language so you can see the exact same search results but the page layout is wrong in English.
I found that the English page is showing the content that is defined under the !is_search and the Hebrew page shows the correct content from the is_search definition that I made.
Another thing that affects the CSS and also a definition used in woocommerce.php is that in Hebrew the body class contains “archive tax-product_cat” and in English those are missing.

Any idea?

maybe it is a problem with interaction with Woocommerce?

Any idea at all?
In Hebrew which is the main language there is no problem at all…

I understand, indeed we are using the custom taxonomies such as the product_cat and product_tag and not the regular wordpress category and tag taxonomies.

Looking forward to your solution!

Is it okay to remove the links that I added above?

I wasn’t aware but the Edit option for posts is available for only one hour after it was posted so can’t erase the links… never mind.

Now after this new version we are almost there! A great improvement.

Now infact the is_search is working and we can see that the “archive” definition is in the body class.
The more important definition is still missing from the body class, it is for the following usage for the layout:

if (in_array('tax-product_cat',$classes)) {

I use this to differentiate between regular search results layout and the layout of this custom filter which is based on the search function.

You think that this can also be resolved? I think that it is still related to the custom taxonomies but you should know better…

While it is not the best solution for me, for now I will change the condition to check if we have “archive” in the body class as in the regular search it doesn’t have it so it will still differentiate the results layout.

Please update me if you managed to fix the tax-product_cat issue.

I wish to thank you now but I will save it for when I mark this topic as solved 🙂