I just tested the link you shared in an incognito browser and I am not seeing the error. Can you please try clearing your cache and check again? Please see my attached screenshot.
The reason you don't see the error because I turned off the debug mode. I turned that on before to show you what the error it gives me.
Anyway, the page is still crashed - this is a case.
Thanks for migrating the site. It seems that your errors are coming from your custom code in the functions.php file. When I switch to a default theme and view the standard WooCommerce category pages, I do not see any errors. Please feel free to check out the test site page here: hidden link
You can switch languages with the footer language switcher to test it out. I tried keeping your custom theme active and activating only WPML and WooCommerce to further test, but this caused a fatal error due to your custom code in your theme's functions.php file. Due to the extent of custom code, at this point I need to suggest you consider contacting one of our certified partners from this link: http://wpml.org/documentation/support/wpml-contractors/
I'm sorry I am unable to provide a custom solution for you, but I hope one of our contractors will be able to sort through the custom code and get this resolved for you.
Hello, the link that you have provided does not contain anywhere output links to taxonomy brand Porsche. I did the same, only additionally created a test page with a link to a taxonomy that has an error. As a result, the error remains even when installing the standard Twenty Nineteen theme. This means that the problem is not in custom code. You can verify this by creating a test page and calling a taxonomy.
For example:
<?php
I created that template and assigned it to the following page: hidden link
I tried to reproduce the issue in the original post where if you set the taxonomy to not translatable, the terms displayed. However, after changing that setting, I still saw the error. So, I disabled WPML and still see the error.
Can you please help me to reproduce the issue on this test site so that I can show our developers the issue that occurs only when the taxonomy is set to Translatable? In other words, can you show me how the code you are using DOES show the terms with the correct settings? I will be able to escalate to our developers once I can see that happening again. Thanks!
The error you are seeing is a separate issue from what this ticket was originally opened for, so I have split the ticket and will address that issue in a new one. Please see my previous reply and let me know how I can reproduce the original issue when the taxonomy is set as translated. Thanks!
We have already gone through this, I answered all these questions. The essence of the problem was clearly described and in the last message it was vividly demonstrated, no matter what topic was set. You named the ticket as - get_terms is not working correctly, which in general has nothing to do with the problem that I described to you. I had no questions about the get_terms function.
