I have just started having the same problem with the DeepL plugin. Any suggestions for a fix?

Afrim Hyseni John Fry Jeff Staflund 

First thing is to review the release notes as the advice in there is to uninstall all your plugins completely before updating.  Then only install plugins that you can see are available for you in the integrated appstore as many have not been updated yet.

This post sheds a little more light on it...  RE: TexTra plugin causes error after latest update to Trados Studio 2022 

But in relation to the ones mentioned in this thread DeepL is fine if you use the correct version, ModernMT almost certainly needs to be updated to support SR1 and MT Enhanced is best replaced with the separate Google and Microsoft plugins as these have been rewritten and will be maintained to support anything new that is available from these providers going forward.  You can find them here:

https://appstore.rws.com/Plugin/174

https://appstore.rws.com/Plugin/179

Hi Paul,

We tried the new Google plugin (with the nice interface) and it worked. Thank you!

After installing the latest version of the Subtitling Studio plugin, I am encountering an error that is causing disruption to my workflow. Whenever I attempt to launch the plugin, an error message pops up, preventing me from accessing its features and functionalities.

I have tried reinstalling the plugin, restarting my system, and ensuring that I meet the necessary system requirements, but the issue persists. I believe it may be a compatibility issue or an installation error.

I would greatly appreciate any assistance or guidance you can provide to resolve this matter. Subtitling Studio is a crucial tool for my subtitling projects, and I would like to resume using it smoothly as soon as possible.

Thank you in advance for your support and attention to this matter.

<SDLErrorDetails time="08.07.2023 06:24:31">
<ErrorMessage>Nie odnaleziono metody: 'Void Sdl.LanguagePlatform.TranslationMemoryApi.FileBasedTranslationMemory..ctor(System.String, System.String, System.Globalization.CultureInfo, System.Globalization.CultureInfo, Sdl.LanguagePlatform.TranslationMemory.FuzzyIndexes, Sdl.LanguagePlatform.Core.Tokenization.BuiltinRecognizers, Sdl.LanguagePlatform.Core.Tokenization.TokenizerFlags, Sdl.LanguagePlatform.TranslationMemory.WordCountFlags, Boolean)'.</ErrorMessage>

I'm having the same issue with the DeepL plugin as Jeff. I removed the old plugin and re-installed, but no luck. I looked at the post you linked to Paul, but let's be honest, translation software shouldn't be this difficult (remember how a while ago we all had to switch to some private version of the RWS App store? Whatever happened with that??)

I'm not a programmer. So how do I get the DeepL plugin to work again? 

Replying to myself because I got it to work just now by going to Add-ins->Plugins, deselecting the DeepLMTProvider tick box, re-launching, then reselecting it, and relaunching again.

Katherine Holly Kirby 

Katherine Holly Kirby said:

translation software shouldn't be this difficult

I agree... and believe me we don't do it on purpose!!  You have no idea how much work this is for us.

Katherine Holly Kirby said:

remember how a while ago we all had to switch to some private version of the RWS App store? Whatever happened with that??

This was needed because we lost the old appstore from one day to the next and so we solved it by using the Private AppStore concept that we added to the software.  Then, we worked on rebuilding the appstore until we had got it to a stage that we could put back the default AppStore and not require the Private AppStore any more.  We are now nearing completion of the next stage to be able to start allowing 3rd party developers to have access to manage their own plugins again.  It's a lot of work behind the scenes and it's not simple, but we are almost in a situation now that will make it possible for us to do whatever we want with this solution and that means all the things users asked for in the past with the old solution but we were simply unable to do it.

I can't really tell you more than that... we're doing our best with a very complicated situation.

Katherine Holly Kirby said:

I'm not a programmer. So how do I get the DeepL plugin to work again? 

You don't have to be a developer, you just have to follow the instructions which are not that difficult.  Delete everything you have in these folders:

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

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

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

Then restart Studio and reinstall them via the integrated AppStore in Trados Studio. This way you will only install the ones that will actually work with SR1. If your apps are not in the list yet then contact the developer via the support link at https://appstore.rws.com/ for the app in question (every developer has some form of contact details) and ask them to update their apps for SR1.

The DeepL app was one of the first to be updated so you really should not be experiencing any problems if you followed the instructions in the release notes... the ones we spend ages compiling and nobody ever reads ;-)

Hey Paul,

Thank you for the quick reply. I definitely appreciate your availability to help out with this stuff. I used to work in operations at a digital music distribution start-up in San Francisco, and I worked closely with the dev team. It's a lot of work integrating all the different specs and bits and bobs, for sure.

You're right, we don't read the release notes, we're busy working at 11 pm! lol

Hey Paul,

Thank you for the quick reply. I definitely appreciate your availability to help out with this stuff. I used to work in operations at a digital music distribution start-up in San Francisco, and I worked closely with the dev team. It's a lot of work integrating all the different specs and bits and bobs, for sure.

You're right, we don't read the release notes, we're busy working at 11 pm! lol