Yes, you will need to reapply the code change after each plugin update, as updates will overwrite the modified files.
If you need more detailed instructions on how to apply the workaround, please let me know, and I’ll be happy to provide them.
Regarding the permanent fix, I cannot provide an exact version number or release date. However, based on the current planning, it is expected to be addressed in a future release somewhere between WCML 5.6.0 and 7.0.
I updated all the plugins, theme and WordPress version. I also added the code I received from your support for the workaround, but now we notice that the woocommerce sidebar is again not showing all the filters.
Also de translations are again missing in product detail.
You can check this url: hidden link
And see the screenshots attached, with every error marked.
Also its very important that the translations where again missing before I updated WPML...
I’m sorry to hear that you’re still experiencing this issue.
Unfortunately, there is no alternative workaround available at the moment. Please make sure that the code workaround described in this reply has been followed carefully:
If the workaround was not applied right away after the update, it’s possible that the same attribute was registered more than once. In that case, you may need to repeat steps 3 and 4 from the workaround to ensure the correct attribute is registered and translated.
On my side, I will add an internal note to our development team requesting that this issue be prioritized. While I cannot guarantee a timeline, I hope it can be addressed in one of our upcoming releases.
Did you get the chance to prioritize to the development team? Because I have 2 new websites coming up that need translation and I'm holding back to get started because the actual problem.
It would be nice if this issue is prioritized for your development team-:).
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Vienna (GMT+02:00)
Hi Kathleen,
Andrey is currently on vacation, so I'll be assisting you in the meantime.
I can see that Andrey has already forwarded this issue to our development team. Please note, however, that we aren't able to influence when a fix will be implemented. The developers determine their own priorities, and at the moment they're focused on completing work for the next major release.
Once that work is finished, we hope to have more information regarding the timeline for addressing this issue. We'll be sure to keep you updated as soon as we receive any news.
