Would it be worth creating a drush command for the translation clone operation?

Rationale: many sites run on systems that can time-out before the (potentially lengthy) cloning operation finishes.

Comments

jeremylichtman created an issue.

james.williams’s picture

james.williams
Location Coventry, UK
commented

Yes! Patches welcome :-)

gomez_in_the_south’s picture

gomez_in_the_south commented

Whilst an option to run via drush would be great, I wanted to point out for those that are having time-out errors (e.g. 504 gateway_timeout), that you can set the following variables to reduce the batch size which can prevent these errors:

translation_clone_entity_translation_batch_size (default 20)
translation_clone_content_translation_batch_size (default 20)
translation_clone_locale_translation_batch_size (default 50)

These can be set with variable_get() in code, or with drush vget from the command line.