Open
Overview of the issue
When using the YITH Booking and Appointment for WooCommerce plugin with WPML, the resources module does not work as expected for translated bookable products. This means resources cannot be displayed properly for products in secondary languages.
Workaround
Currently, there is no direct workaround to resolve this issue, as the resources module in YITH Booking is not integrated with WPML.
Here’s what you can do:
- Open a new ticket in our support forum explaining the issue. Mention this errata for reference.
- Reach out to YITH’s support team and report the compatibility issue with their resources module and WPML.
Hello, I am using WPML for translation and YITH Booking and Appointment for WooCommerce for booking. I am translating Resources and I am also translating the products using WooCommerce Multilingual & Multicurrency. However, the Resources themselves are not displayed in the translated products. Could you please help me? When I switch the language, the “Type of visit” (Resource) disappears.
Hi Alexander,
We reported this issue to YITH, but unfortunately, they won’t be able to include it in their next release. I recommend reaching out to their support team, as additional client requests for this feature may increase its priority. Please also start a chat on our support forum and mention this errata to the supporter who assists you.
Thank you Nikolas – you are awesome! All team!
This issue / problem disappointingly still exists and has been existing for a long time now. I reported the issue back in September 2024 and they still did not fix it!
This is a crucial function of YITH Booking and Appointment for WooCommerce and I really really hope they can solve the issue near-term.
If anybody has a workaround or was able to solve the problem, please let me know!!!! Thanks!
Hi Thomas,
We’ve already reported the issue to the YITH team. Could you please open a ticket on our support forum and mention this errata page? One of our supporters will assist you further.
I opened a ticket with the WPML support. A workaround was found, which worked absolutely fine!!!! Amazing support!
I think this could be interesting to other people as well…