When I try to edit entries in MultiTerm from inside Studio, I get a script error (see picture). It is not affecting the functionality, i.e. the entry can be edited and saved, but it is annoying to see this error message every time.
This error does not appear when I edit entries in MultiTerm directly.
Regards,
Peter Bolin
Sweden
Hi Peter Bolin Pascal Pauly Alison Field
This is a problem with CU6. I expect the development team to release a fix for this next week. In the meantime you could revert to CU5 by removing the last update:
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Peter Bolin Pascal Pauly Alison Field
This is a problem with CU6. I expect the development team to release a fix for this next week. In the meantime you could revert to CU5 by removing the last update:
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Thanks Paul ,
I have a funny feeling that it was already happening before I updated to CU6... can't be sure.
What I can say is that it doesn't go away with a Windows Repair. It happens whenever I add a new term or modify an existing one in Translation Mode.*
When in Review mode, it happens specifically when I add a second target term to an existing term in the Termbase Viewer window. I just click 'Yes' then can continue normally. It happens in the Default layout and Flags layout so probably all layouts.
Have a good weekend one and all!
Ali :)
(*Edited, I had only tried it in Review mode till today when I'm translating...)
Hi guys,
I've been discussing a similar though not identical problem with user Sam Mass here in the SDL Trados Studio group:
Cannot edit a term in Termbase Viewer
The difference there is that he can't continue and edit the term after clicking 'Yes'. I have suggested he changes from Default layout to Flags layout to see if that then works OK for him.
Here's the error he's getting, exactly the same as the one I'm getting:
I thought it would be helpful to him to receive notifications on this thread for if and when a fix is found, and bring the two threads together into one.
BTW I removed CU6 and the problem is still occurring in CU5 as I thought I remembered.
All the best to one and all!
Ali
[:D]
Translate
