if the customer is not perfectly happy with the translation, he should be able to request improvement throgh a feedback loop.
The new API from OHT provides this functionality and we should add it to the UI.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | tmgmt_oht-oht_comments-1894046-2.patch | 6.82 KB | blueminds |
| #1 | tmgmt_oht-oht_comments-1894046-1.patch | 6.51 KB | blueminds |
Comments
Comment #1
blueminds commentedThere is no reject/review thing in the workflow. The only thing we can do is to submit comments to a project. See the attached patch for the functionality.
Comments are attached to the review screen. The reason is that we map job item to oht project and there is no other screen dealing with job item itself. Also it makes sense to provide comment feature during the review process.
Comment #2
blueminds commentedComment #3
berdirYou should be able to use the reviewForm() method of the translator UI controller. That's exactly why we added it :)
Then you don't need the translator check (which is wrong, name can be anything, the plugin must be oht ;))
%placeholders are automatically check_plain()'d. So you must not call it again or it would be double encoded.
I think any id can be accessed with a #fragment, so you can just add the id to the fieldset.
You can use #theme => table and #rows => $rows. And maybe add an #empty => t('No comments')?
Not sure if drupal_set_message() is check_plain()'ed. Also, not sure what the exception exactly returns, maybe add something like "Failed to submit comment: @error".
Comment #4
blueminds commentedComments implemented
Comment #5
berdirThanks, commited.