I wonder why the direct import of translation table (omeka_multilanguage_translations) via MySQL does not give a proper effect. Some of the metadata fields (for Items) gain their translations this way, but some of them do not. There are rows in the database with translation data, but some of them are not visible/available either in the admin panel or after switching locale on the public view. Of course items and fields ids are correct in the table being imported.
I wonder why the direct import of translation table (omeka_multilanguage_translations) via MySQL does not give a proper effect. Some of the metadata fields (for Items) gain their translations this way, but some of them do not. There are rows in the database with translation data, but some of them are not visible/available either in the admin panel or after switching locale on the public view. Of course items and fields ids are correct in the table being imported.