- Issue created by @heddn
This is working but the messages are only added to the job once its translation comes back/gets accepted.
I wonder if we should write an update hook or even a small form or hook_cron that allows scanning for such jobs (which are pointing to irrelevant workspaces), lists and updates them. That would allow a more immediate feedback on such jobs to users.
If we wanted to improve this situation a bit more, we could implement
hook_workspace_update()
and possiblehook_workspace_delete()
in this module to display/log warnings referring to the jobs and also updating the current jobs adding the message that is added in the MR.- heddn Nicaragua
I _think_ the normal use case where this happens is when this module is installed after various translations were sent off. Translations come back and are accepted via a cron job. No one would visit the job items page to see any errors/warnings until after the jobs _still_ aren't accepted. So I think what we have here covers the majority use case. If we can't find a workspace, we could just dump translations into Live, but that seems error prone and unexpected. Better to leave in an error state and have the site owner cancel or edit the job to manually assign the correct workspace and re-process the jobs.