This project is not covered by Drupal’s security advisory policy.
At one step you create node with translations. Taxonomy and other cck
fields bind to these translations too.
LangsAtOnce creates additional title, body fields for selected languages. So
when you go "create node" page you face with normal fields and
title/body areas. These additional ares will be added as translations.
When you want to add a say lyrics with spanish, english and turkish
translations. You should create node. Then click translate, add eng
translation, click translate add tr version.
LangsAtOnce creates additional title, body fields for these languages. So
when you enter create lyrics page you face with 1 main content area, and
3 title/body areas.
At one step you create node with translations. Taxonomy and other cck
fields bind to these translations too.
My module is not intended to update/delete/validate etc. (cause if you
dont enter a turkish translation It's copied from orginal title, If you
dont fill the turkish body it isnt inserted). If you want to update a
translation you'd go with normal translation system.
Project information
- Project categories: Content editing experience, Import and export
- Created by nerkn on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
