Closed (fixed)
Project:
Translation Management Tool
Version:
8.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
23 Feb 2016 at 17:50 UTC
Updated:
30 Apr 2016 at 14:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
edurenye commentedComment #3
miro_dietikerThis is for the review form.
Comment #4
mbovan commentedI added a warning message in case job item is in Active/Review state and explaining the situation.
I think we should allow the administrator/user to change translation, especially when there is option to "Revert changes", which is a kind of hack to accept received ones.
The screenshot

Not related to this issue, but revision messages can be easily too long because we display full text in it... Maybe we can put it in a (one more?!) details tab...
Comment #5
mbovan commentedUpdated the state condition and the message:

Comment #6
edurenye commentedIf we let the user edit it, we ought inform him that his changes can be overwrite by the translation, not just that his changes will override the translation.
Although, another option also could be to not let the user edit the translation at all.
I think, we agreed with @miro_dietiker, that the second, it's the best option.
Comment #7
mbovan commentedHm, I never managed to do this: "If we let the user edit it, we ought inform him that his changes can be overwriten by the translation"
We can change to "disabled" for a user as well.
In case translator is too lazy we can't do anything with a job/translation except waiting or abort/delete it?
Comment #8
berdirWe should probably wait with this task until we have preview support in the local translator that will use this. Then we will be able to properly test this manually. Right now, the patch isn't really doing what we mean.
Comment #9
edurenye commentedPostponed until this issue is fixed #2682337: Add the preview feature to translator local
Comment #10
mbovan commented#2682337: Add the preview feature to translator local was fixed so we can work on this one.
Comment #11
mbovan commentedUpdated the patch to disable translation fields and data items actions.
No tests yet. Is the message too technical?

Comment #12
berdirnot sure if we use data items in the UI elsewhere. Maybe miro has an idea on the label?
We could go just this job item, it doesn't really matter if it's just part or everything for the user.
We could use $form_state get/set to avoid adding another argument here. we will do that too in the format/permission issue.
Comment #13
miro_dietikerTo add a form element always and hide it with #access is a good practice for extensibility.
However, adding arbitrary messages and hiding them with #access is strange. It should only be added if needed.
Comment #14
miro_dietikerI would simply refer to "translations". ;-)
Comment #15
edurenye commentedRebased and did those changes.
Comment #16
johnchqueMissing statement is: As a result, you can not accept the item while preliminary...
Also the user should have awareness that posting a change will be overwritten by the user with any future update. (Sure, we have revisions..)
Comment #17
edurenye commentedAdded tests and removed the "Save" button also if all the data items are in preliminary state.
We discussed about last comment and we don't need to change the texts as it's not possible to accept or change anything in this state.
Comment #18
berdirThanks, committed with the following change: