No, it doesn’t re-copy.
It is possible to manually delete the template variables associated with a language (content_langid, pagetitle_langid, etc.) They can be re-created at any time by pressing submit on the Modules>YAMS>Multilingual Templates tab.
I’d do it as follows. Please note that this will delete any existing English and Indonesian language content, but the standard document fields will be untouched.
So, how to make:
1. Original document content => Id document content
2. En document content => deleted.
3. Id document content <= auto-sync => original document content
Yes. TinyMCE is normally installed by default with MODx. You have to make sure that it is activated under Tools > Configuration > Interface & Features > Enable Editor ..., and you must also make sure that your documents have the ’Rich Text’ property selected on the Settings tab.
BTW,
Can I use TinyMCE in YAMS?
It works.
I’d do it as follows. Please note that this will delete any existing English and Indonesian language content, but the standard document fields will be untouched.
- Go to Modules > YAMS > Language Settings. Make sure Id is set as the default language.
- Go to Elements > Manage Elements > Template Variables.
- Delete *_en (alias_en, content_en, etc.). This achieves point 2 above.
- Delete *_Id (alias_Id, content_Id, etc.).
- Go to Modules > YAMS > Multilingual Template and press Update. This will copy all content from your standard document fields to your Id language fields for all multilingual documents.
Next version, may be?
Unfortunately, with the exception of the pagetitle there is no mechanism in YAMS for keeping the document content fields synchronised with the default language fields.
My bad. I used to turn this off, since RTE always break the & chars. It works.
Yes. TinyMCE is normally installed by default with MODx. You have to make sure that it is activated under Tools > Configuration > Interface & Features > Enable Editor ..., and you must also make sure that your documents have the ’Rich Text’ property selected on the Settings tab.
Multilingual documents don’t use the standard document variables at all. They become redundant. Instead they use the multilingual template variables: pagetitle_{langId}, content_{langId}, etc. There is no linking of the data in the default language tvs to the data in the standard document variables - although I can see why this might be considered a good thing. It would be possible to switch the document back to monolingual and have it up to date with the default language content only.
Or, perhaps the default lang doesn’t have its separate TV and contents. It just simply an empty variable that’s (let say) hyperlinked to the ModX’s origin content.