Probably our fault, but after setting up 7 languages on our live server and creating translation sets and translations, then sending these off to our translation house we have noticed that we have lost the translation sets on live! Can anyone advise?
We did have a hotfix to live after these were created which would have included a usync settings import, but not a content import.
The files we created do still exist in the /media/xliff_translations folder.
Does anyone know of a way to get these jobs back into Translation Manager and any ideas what happened here? Did language id's get updated from a dev environment any sever the links on live?
To summarise: languages still ok on live, files still in xliff folder, translation sets missing along with the jobs for those sets. I can create a new translation set with the same languages involved but the jobs don't get picked up.
I sounds like something has wiped the data from the database 😟
So the sets are in a translate_sets table, (and maybe others are missing too.
Best bet would see if you have a backup of these tables before any application of a fix,
if you don't you might be able to hack a job back into the table, but it depends on what tables you have remaining and what is in them .
if there is data in the tranlate_nodes and translate_jobs tables then hacking the setKey value might get the jobs back (assuming you've recreated the sets), but if those are missing then its not an easy job.
One hope is most translation companies are using Translation Memory - so if you send them the same content again, they don't actually translate it mannually the translation memory simply puts in all the previously translated values and returns the file.
so it might be quicker to resend the jobs to your provider and have them return them from memory - but i would check this with them fisrt.
Yeah I can confirm that those tables don't contain the new data, although I could have sworn that we didn't restore a database after that point.
Ah well, I will put this one down to experience and re-create all the sets.
Thanks Kevin!
Translation Sets missing on live (help!)
Probably our fault, but after setting up 7 languages on our live server and creating translation sets and translations, then sending these off to our translation house we have noticed that we have lost the translation sets on live! Can anyone advise? We did have a hotfix to live after these were created which would have included a usync settings import, but not a content import. The files we created do still exist in the /media/xliff_translations folder. Does anyone know of a way to get these jobs back into Translation Manager and any ideas what happened here? Did language id's get updated from a dev environment any sever the links on live?
To summarise: languages still ok on live, files still in xliff folder, translation sets missing along with the jobs for those sets. I can create a new translation set with the same languages involved but the jobs don't get picked up.
Hi Sam,
I sounds like something has wiped the data from the database 😟
So the sets are in a
translate_setstable, (and maybe others are missing too.Best bet would see if you have a backup of these tables before any application of a fix,
if you don't you might be able to hack a job back into the table, but it depends on what tables you have remaining and what is in them .
if there is data in the
tranlate_nodesandtranslate_jobstables then hacking thesetKeyvalue might get the jobs back (assuming you've recreated the sets), but if those are missing then its not an easy job.One hope is most translation companies are using Translation Memory - so if you send them the same content again, they don't actually translate it mannually the translation memory simply puts in all the previously translated values and returns the file.
so it might be quicker to resend the jobs to your provider and have them return them from memory - but i would check this with them fisrt.
Yeah I can confirm that those tables don't contain the new data, although I could have sworn that we didn't restore a database after that point. Ah well, I will put this one down to experience and re-create all the sets. Thanks Kevin!
is working on a reply...