Multiple Translation sets: a couple of feature requests
Hi,
We have a couple of feature requests. Please let us know if any of the features already exist.
We have the following multi-site scenario setup:-
en-US -> es-US -> es-MX
We have set up a couple of translation sets to handle this scenario. Any new content in en-US triggers a job in es-US. Similarly any new content in es-US triggers a job in es-MX.
However, we would love to have the following two features:-
When a translation manager approves and publishes a job that
publishes to es-US, it should automatically trigger a job for es-MX.
Allow the notifications settings to be specified per translation set
rather than for the entire setup.
Also, for the Pending Translations notification is there a way to have a single email rather than one per translation item.
1 : Out of the box if the (links between the pages are in place*) - when the es-US job is approved items should be placed into the pending items list for your es-MX site - where you could create the job.
Translation manager won't automatically create the job for these links, but it could be programmed to, there are events you can listen for that are fired when jobs are approved, that could be used to create the MX job from the nodes (TranslationJobService.Published might be of use if you go down this path)
it's probably a bit unique to your setup so i am not sure it is something we would put into the core product.
2 : improving notifications is in our plans - we have been working on a better way to offer granular notifications (things like per set settings, and notifying the person who created the job) - these changes will alter the settings a bit so will likely be in the next point release (e.g 2.3) we don't have a timescale for that just now.
links:
*I just tested this and it does work, but it can depend on how your sites where created, if es-MX was created as a copy of en-US then the internal links (relations) between es-US and es-MX won't exist so when a node is updated in es-MX it won't trigger the automatic creation of the pending item in es-MX.
if this is happening the quickest way to fix is to have es-MX be a copy of es-US - if you can't do that, then maybe the linked pages package could help.
Multiple Translation sets: a couple of feature requests
Hi,
We have a couple of feature requests. Please let us know if any of the features already exist.
We have the following multi-site scenario setup:- en-US -> es-US -> es-MX
We have set up a couple of translation sets to handle this scenario. Any new content in en-US triggers a job in es-US. Similarly any new content in es-US triggers a job in es-MX.
However, we would love to have the following two features:-
Also, for the Pending Translations notification is there a way to have a single email rather than one per translation item.
Thanks!
Hi,
1 : Out of the box if the (links between the pages are in place*) - when the es-US job is approved items should be placed into the pending items list for your es-MX site - where you could create the job.
Translation manager won't automatically create the job for these links, but it could be programmed to, there are events you can listen for that are fired when jobs are approved, that could be used to create the MX job from the nodes (
TranslationJobService.Publishedmight be of use if you go down this path)it's probably a bit unique to your setup so i am not sure it is something we would put into the core product.
2 : improving notifications is in our plans - we have been working on a better way to offer granular notifications (things like per set settings, and notifying the person who created the job) - these changes will alter the settings a bit so will likely be in the next point release (e.g 2.3) we don't have a timescale for that just now.
links: *I just tested this and it does work, but it can depend on how your sites where created, if es-MX was created as a copy of en-US then the internal links (relations) between es-US and es-MX won't exist so when a node is updated in es-MX it won't trigger the automatic creation of the pending item in es-MX. if this is happening the quickest way to fix is to have es-MX be a copy of es-US - if you can't do that, then maybe the linked pages package could help.
is working on a reply...