Hello,
Thanks for your hint.
First I manually deleted all por-PT second translation articles. So, only single language articles remained. They were por-PT OR por-BR, not both.
I stoped ezpublish then dumped sql from db. (complete and delayed inserts, , drop db, etc, slow and big but reliable)
After, used vim (it can edit multimegabytes files that crashes other editors) to change all but first por-PT instances for por-BR.
The first occurrence is the ez configuration showing wich translations are available.
Restored the database from the new sql dump and restarted Ezpub. Cleared all caches.
It has been working for some hours and I can edit the old articles. They are showing por-BR as the only translation.
wow, it was a brain surgery.
I will test more, but I 'guess' it is ok.
Is there any hidden catch about this solution?
Many thanks. Andre Felipe
---
A Debian user never dies. Issues a last command:
shutdown -h now
Hello,
I discovered a drawback.
The article images, and other images became invisible.
The 'right' way to overcome this is BEFORE changing master translation, to ADD the new translation to all articles.
Then after the master translation changing, delete the old translation.
The images are stored in /var/storage using directories associated with translation and a control code.
Simply changing its suffix to new translation does not work.
The other quick and dirt mode is using ezpublish to edit each image, re uploading each one to each image object. This is dirty. will leave wrong translation subdirs, but is faster.
i suggest the most labarious way. it is cleaner.
Regards. Andre Felipe
---
A Debian user never dies. Issues a last command:
shutdown -h now