ProcessTranslatePage

[robert]

I created a companion module for Fluency to translate all fields on a page at once:

https://github.com/robertweiss/ProcessTranslatePage

You can find the corresponding conversation about it in the Fluency thread (link below), but I decided to add the module to the official list so others who have a need for this have an easier time finding it.

 

[Roych]

Hello,

I always get this error after instaling the module, any ideas?

Notice: Undefined index: pw_language_1022  ----   site/modules/ProcessTranslatePage/ProcessTranslatePage.module.php on line 115

Thank you

R

[robert]

Hi Roych,

thanks for your feedback! I found the bug – I falsely assumed that the default language id in processwire is always 1022 (which is obviously not the case …). I pushed a bugfix to the github repo (https://github.com/robertweiss/ProcessTranslatePage) and changed the version to 0.0.3. Could you try the bugfix and see if it works for you now?

[Roych]

Thank you, It looks like it is working great now. Great module btw! 😉

R

[robert]

Just released v0.5 which includes the following new features:

• Exclude fields: choose fields which should not be translated
• Exclude languages: choose languages which should not be translated to
• Show Single Target Language Buttons: Show all target languages as single buttons in the save dropdown instead of having only one button for all translations

Thanks to @Ivan Gretsky for proposing these additions!

[theoretic]

Hello Robert! Thanks for a perfect module! I've made some changes to it (e.g. possibility to set the source language in module settings), how can i collaborate with You?

[robert]

Oh cool, sounds good 🙂 Your addition might be a good fit for the open issue by Ivan Gretsky: https://github.com/robertweiss/ProcessTranslatePage/issues/3 – would it be an option for you to fork my repository on Github so we can merge via a pull request?

[studioweb]

Hi Robert, nice work! Feature request: a option to translate the page/seo names. This should only be translated once so there should be a way to save this into the page meta data perhaps ;)

 

[robert]

@studiowebThanks 🙂 To prevent possible misunderstandings: you’re talking about the $page->name field, right? This is indeed a special case as it is the only translatable system field I could think of. I would suggest the following mechanism: only translate the page name if the target language name is identical to the source language (and therefore: not translated yet) – and allow users to switch it off in the settings to prevent possible conflicts with other modules modifying the name field on save (e.g. ProcessSetupPageName). 

[robert]

@studioweb I had a deeper look into the page->name feature request and decided to not include the automatic translation of this field. As I suspected in my last post, there exists already a better solution for this 😅 If you install the module https://processwire.com/modules/process-setup-page-name/ and activate its option ›Update the name of existing pages‹, the name field will be updated in all languages whenever you change the corresponding field (normally title). 

[robert]

v0.6 is released with the following changes:

• New setting: Source language (thx for the idea to @Ivan Gretsky and for the pull request to @theoretic)
• Languages for source and exclude can only be selected if they have been defined in the fluency config first
• I had to do some refactoring of the translation strings and the module config, so please validate/correct your settings after the update to v0.6!

[bernhard]

Any screenshots to get a quick impression? 🙂 

[robert]

@bernhardSure 🙂 

Module Config  (sorry for the mixed labeling, I have the german language pack installed 😅 ):

Publish + Translate to all target languages at once:

Publish + Translate to single languages (on the left side of the arrow: source language, right: all available (aka not excluded) target languages):

[bernhard]

Very nice, thx, I'll try that asap on my new website 🙂 Does it translate all fields after save or only ones that changed during page edit? Sorry if that was already mentioned - I didn't find that information.

[robert]

Translating only changed fields is quite a good idea, I just added it in v0.7 😄

• New radio option: Write Mode (replaces the checkbox Overwrite Existing Translation)
  • Translate only if target field is empty
  • Translate only changed fields
  • Overwrite all target fields

Caution: the »Changed fields«-option support is currently only one level deep. If you change any value inside a Repeater(-Matrix) or FieldsetPage field, the complete field will be translated. If anybody knows how to get the names of nested fields that changed inside the afterPages::saved hook, please let me know 🤔