Bernat Torras (a11n)
Forum Replies Created
-
Hi damiasanx and kiskrtek,
Can you try it with WPML Multilingual CMS 3.1.8.2? Try to delete your current ‘Strings Translation’ and ‘Translation Management’ plugins, and download+activate them again in Plugins>Add New>Commercial.
Let us know the results. 🙂
Thanks,
BernatHi Jorge Ele,
It definitely looks like a compatibility problem. I’ve checked our compatibility list and we haven’t worked with that plugin yet… Can you paste the url of the plugin? This way we’ll be able to add it to our to-do list and contact the author to join our compatibility program. Once he joins we will work together to provide the best approach to fix this issue.
Thanks for reporting it!
PS: We’ll update you as soon as we have any update.
Bernat
Hi Latumweb,
Yes, I’m afraid it is a known bug in the latest version. We’ve already fixed it on our dev version and is ready to be included on next wcml update. I can’t provide you an estimate date yet, but we’re currently on QA process so if everything is ok it should be published soon. 🙂
Thanks for reporting,
BernatHi ttan,
I’m sorry but no… This process always takes different amount of time as it depends on the complexity of the plugin and the author feedback… I can just tell you that we’ll try to prioritize it as much as we can!
Thanks,
BernatHi tttan,
We’ve added this issue to our compatibility list. We’ll contact the authors to work with them to find the best approach to make it 100% compatible with WPML. We’ll let you know as soon as it is fixed (you can also keep an eye on their updates).
Thanks! 🙂
Hi andrefgneves,
Thanks for reporting. Could you open a ticket in wpml.org support forum providing a some details about it? We’re specially interested with ‘steps to replicate’ and your plugin versions. This way we’ll be able to check if its a bug and fix it for the new updates. 🙂
Thanks,
BernatThanks for letting us know. I’m adding it to our todo list and we’ll work to get it fixed. 🙂
Thanks!
BernatHI tttan,
Just to be sure, could you send us the url of the extension so we can check? Also, could you describe the issues that you’re experiencing?
Thanks,
BernatHi myefreelance,
As commented in your previous ticket, WooCommerce 2.0.X is almost a year old… Would it be possible to update to a newer version and check if you’re still able to replicate the issue? Also, could you describe us when does that error appear?
Thanks,
BernatHi myefreelance,
Thanks for reporting. Our updates are supposed to work with latest WooCommerce versions and the last 2.0.X WooCommerce version was released almost a year ago. Since then, many upgrades have been made to WC and WCML, so if anybody updates wcml to 3.3.4 he should also update WooCommerce. Anyway, could you paste the error and describe when its appearing? We’ll take note of it and consider applying some fix! 🙂
Thanks,
BernatHI ,
Your issue can be related to an existing bug in latest WPML version. Can you check if applying the suggested fix described here http://wpml.org/errata/maximum-function-nesting-or-allowed-memory-size-exhausted/ fixes the issue?
Thanks,
BernatHi imdreamer,
We fixed this issue in our WCML 3.3.4 update. Please try to update and check if it works. 🙂
Thanks,
BernatHi all,
I suggest you to open a new ticket in the wpml.org forum. From there we’ll able to log in your site (if you agree to share your credentials privately with us) and test&debug your issues directly. Being a priority issue I’m sure we’ll be able to apply some temporary fix to your site.
Thanks,
BernatHi meenashah,
Glad to read its working now. 🙂
As for the 404 page, you should try to save your permalinks again and be sure that all your strings appearing in Permalinks page are translated in WPML>Strings Translation. You can also try to delete the ‘product-category’ translation (and the other permalink slugs if you want) and try to translate again (make sure that the translations are marked as complete). If it is still not working, could you paste here the generated urls in both languages (specifying which works and which not).
You could also check if you’re still able to replicate the issue with any default WP theme (like twentyfourteen) or with all the plugins deactivated (except woocommerce & wpml plugins). If the issue gets solved it will mean that it is a compatibility problem. In that case you should tell us the theme/plugin affected and we’ll work with the authors to make it compatible.
I’m sorry but the only way I can ask you for credentials is in the wpml.org forum… I suggest you to ask your client to apply the ‘forgot password’ form to get his credentials back and post a ticket in the forum. 🙂 (https://wpml.org/wp-login.php?action=lostpassword)
Thanks,
BernatHi GrimmGuest and zigorob,
Thanks for reporting! We’re taking note and adding it to our priority list. We’ll update WooCommerce Multilingual with a new version soon, so I’m sure you’ll be able to update without any problem very soon. 🙂
Thanks,
Bernat