Rating: 5 stars
Why are there so many bad experiences here with this translation plugin for Caldera Forms?
Maybe it’s a bit misleading that there is a notice that says that this plugin would be compatible with WPML?
My experience is that it works well with the free Polylang plugin. Only it doesn’t work for the message when sending a form successfully. Maybe this is because that is not a form field? This can still be solved by using a filter script in the functions.php of the used theme.
Even for a plugin that is more than 3 years old I think it deserves at least 5 stars. But in combination with free Polylang!
Rating: 3 stars
I say this, on a positive note, because I have it working well in combination with WPML. I won’t say it’s brilliant, as I like it to be from Caldera looking at the Forms UI and UX, but I realised that making a form for each language separately wasn’t the answer to my predicament of servicing three languages (originally four). I got it to work, it needed some tweaking in the form as well -Auto Responder in three languages and a two conditions (to serve English or German or not at all, which would be our default: Dutch)- and that’s all.
Some more attention to Translations would be appreciated from Caldera after reading the other reviews.
Rating: 1 star
Buggy for a long time.
]]>Rating: 1 star
Unfortunately it just doesn’t work. Hopefully it will work in the future with PolyLang.
]]>Rating: 2 stars
I don’t like giving negative reviews. But because I love Caldera Forms so much, I am hoping this is rather considered as positive crit rather than a negative review.
While it is great that you offer a free translation plugin ( I was soooo excited), it is very confusing and not user friendly at all.
I do believe, if you used this plugin to rather bridge the gap between PolyLang or WPML or other translation plugins, it would be WAAAAY better.
As it stands, maintaining translations is time consuming. Now to create a translation on every form and field… No… does not work for me. Too tedious.
I landed up rebuilding my contact forms into the languages I need manually.
(I have large contact forms).
BUT—-Thank you for Caldra forms. The greatest form builder available.
]]>Rating: 1 star
Doesn’t work well at all. It makes the whole Caldera plugin useless for us. Waste of time. We’ll probably have to migrate to Contact Form 7 or something.
]]>Rating: 1 star
Just reran on another website, doesn’t work -at all-
]]>Rating: 1 star
This plugin shouldn’t be needed at all as the main Caldera Forms plugin should be WPML compatible out of the box.
]]>Rating: 1 star
Imagine you translate a long form into different languages. Then imagine you change a custom class or add/remove an option from the form. Now imagine all your translations gone.
Every form save (even if nothing changes) will overwrite the translation because this plugin saves the translation information directly into the form object. Once you save it from inside the form, the translations disappear. This plugin does not hold up to the otherwise good standards of the caldera forms.
Rating: 1 star
The original plugin Caldera Forms works beautifully although with some limitations on the free version.
This add-on for translations is a good idea in theory but lacks too many functionalities to be considered useful. If you read the support threads you will understand that it can’t be a proper solution for a website with multilingual needs.
I’ve installed and only in 5m of use i could find:
– bug in saving translations: it accepts your manual introduction and it displays those same translations in the front end, but if you need to edit, the backend didn’t store any of your work and it resets the translations you had previously inserted
– no option to translate html strings. If you create a form using a template, like contact, you have an header and a middle string that are html fields who’s value needs to be updated – this add-on doesn’t provide such option, and in the tutorial of the site they don’t even show the final result of the explanation because they know it will raise questions about the html fields lack of support.
Hope these issues get fixed because it would be a sweet add-on to have.
thank you,
]]>