María Estévez 

María Estévez said:

I feel like part of a therapy group "Trados issues" or "Insomnia x Trados"

Indeed... but perhaps you need to join the "Read the instructions" group :-)

If you read the release notes before installing you'd have seen the part that suggested you remove all your plugins before upgrading and then reinstall them.  This way you have the latest apps that will be compatible with SR1.

Please delete the following folders and then reinstall your plugins after making sure you have the latest ones for your product, either from the appstore at https://appstore.rws.com/ or by using the integrated appstore in Trados Studio:

%APPDATA%\Trados\Trados Studio\17\Plugins

%LOCALAPPDATA%\Trados\Trados Studio\17\Plugins

c:\ProgramData\Trados\Trados Studio\17\Plugins

María Estévez said:

I removed Language Weaver (and I had to pay 100 USD extra for the use I make of it)

You did not remove Language Weaver.  You removed, or think you removed, the plugin for accessing Language Weaver.  You can use Language Weaver without the plugin since it's native to Trados Studio.  The plugin does offer more features, but Trados Studio is getting pretty close to being the same.

Thank you, Paul, for your reply. I feel happy now that you say I can use Language Weaver because it is really useful to me. Now that you mention this, you're right, I had read about removing the plugins, but the day I did it, I had totally forgotten. And in fact, I feel that these things complicate our lives. Why do I have to remove things for an update? These should be done by people from Trados, and we should only update the program. Now Trados is asking me to update to the latest version, and I won't, because I don't want to be stopped from using it.

Thanks for dedicating your time with this reply. Next time, I'll pay way more attention.

Best regards

María Estévez 

María Estévez said:

Why do I have to remove things for an update?

As highlighted in the release notes, SR1 carried "breaking changes" affecting the use of APIs. These are alterations to Trados Studio that may disrupt existing functionality or behaviour, possibly causing applications like plugins that depend on the API to function improperly or cease working.

While we strive to avoid these changes as much as possible, they're sometimes necessary despite the potential inconvenience to developers, who then need to modify their code to fit the new operations. Also, as your question rightfully shows, such changes can pose challenges to our users.

Nonetheless, substantial system changes or considerable enhancements in functionality or security can sometimes justify these disruptions. In this case, we're making these changes to future-proof the product and to incorporate many of the long-standing requests from our ideas site.

We understand it's an uncomfortable process for everyone, ourselves included. However, our priority is to ensure a more robust and efficient product in the long term, even though this might require temporary adjustments. We appreciate your understanding and patience.

María Estévez said:

These should be done by people from Trados, and we should only update the program.

In an ideal scenario, you're absolutely correct. However, plugins can be developed by anyone, and we don't have access to their source code. Therefore, if breaking changes are necessary, the responsibility to make the appropriate adjustments lies with the plugin developers.

We do our best to outline the potential impact and provide guidance in the release notes. As you've mentioned though, the significance of these changes can sometimes be overlooked, leading to complications during the upgrade process even if the release notes are read.

I hope this clarifies this complex matter somewhat. The bottom line is that nobody desires to inflict these kinds of challenges, but they're sometimes necessary for long-term improvements. Over time, we trust the benefits will become evident to all of us!