Under Community Review

Update: we will revisit this idea to prioritize it against a few others in our next planning session for early 2018.

I'm not sure we'll pick this up in time for Sites 9, but in the meantime I'm looking for feedback on the specific status preferred. See my comment below.

Translation Result Status, for nothing submitted

When you send items for translation which do not need translation, rather than seeing an error in the status queue it would be good to show a positive status, e.g. Already Translated

Ryan O'Dell
Parents

  • Ideally the translation job would report status of each item, but we don't have a UI screen for this right now. We do have multi-error reporting screens for BluePrint move up/down (and I think Localization), but it's not generalized (and TMs error is really just a label in the job's screen itself).

    Maybe we could improve the message for certain use cases--where all of the items selected for the job have nothing to translate or they've already been translated. But when do you see this most often? When an editor sends a single item, when there are multiple items based on the same schema (with no translatable fields), or perhaps when the "already translate" checkbox isn't checked?

Comment

  • Ideally the translation job would report status of each item, but we don't have a UI screen for this right now. We do have multi-error reporting screens for BluePrint move up/down (and I think Localization), but it's not generalized (and TMs error is really just a label in the job's screen itself).

    Maybe we could improve the message for certain use cases--where all of the items selected for the job have nothing to translate or they've already been translated. But when do you see this most often? When an editor sends a single item, when there are multiple items based on the same schema (with no translatable fields), or perhaps when the "already translate" checkbox isn't checked?

Children
No Data