We are experiencing an issue when activating the `gravityforms-multilingual` plugin; it hangs and eventually times out. I can see MySQL under heavy load, but once it eventually settles down I can see that it's added about ~19,000 strings to WPML String Translation.
We have ~11 active Gravity Forms, and ~19 in the Trash. Each form has a 'US State' drop-down field, as well as a 'Country' field, of course these contain a lot of options. I can see the label and value both get added as translatable strings, for every country/state for every form- including trashed ones.
We end up with about 30 new domains, one for each form (including the trashed forms), each with roughly 660 strings in. See attached image.
Is there any way to prevent it from translating these particular fields, or perhaps share the translated fields/choices between each form? We can't realistically expect our translators to translate every state & country twice every single time we add a new form. Eventually we may end up with 100s of forms, so we'd have over 600 fields each time.
Thanks,
Alex
---
FYI: Each time I test this out, I restore my DB from a backup so it's fresh each time. I've tried activating the plugin with MySQL query logging enabled and I can see it rattling through the list of countries many, many times. All environments face the same problem, but my local environment has the timeout threshold set far higher so I can debug it.
We're already using the Advanced Translation Editor, so if those form field strings are auto-populated from memory then that should be acceptable.
My main problem though is upon activation of the plugin, the website essentially crashes as it tries to create 19k translatable strings. Presumably every time we create a new form going forwards, it'll also churn through the creation of a further 600 strings. I'm assuming there's no avoiding this?
It would be nice if we could activate the plugin without it automatically running this process. WPML doesn't pull out all strings for every post on activation does it, so why does it do this for Gravity Forms? Can't it create them as I set up the translation for each form?
Currently, each GF form will be registered automatically with the corresponding domain in String Translation. And there isn't a way to prevent this. There is a feature request to prevent this process and I will add this ticket to increase the priority.
I will update you here once I have any information.
