Unsigned plugins not available through the API in 2022

I'm updating old project automation code to Studio 2022, and I've run into a little problem. The project automation code in question runs the Pretranslate task with an in-house translation provider plugin, which is unsigned. This worked fine in Trados 2019, but in 2022 the same code produces an exception with the message "No translation provider factory found for uri XXXXX." The same plugin works fine when it is used normally in the actual Trados application (after clicking yes in the unsigned plugin window, of course). I also noticed that when I call TranslationProviderManager.GetTranslationProviderFactories() in the project automation code, the unsigned plugin factory is not included in results (I also tried with some other unsigned plugins, and their factories were also missing). If Trados is started normally and the unsigned plugin is accepted, its factory does show up in TranslationProviderManager.GetTranslationProviderFactories() results.

Is it still possible to use unsigned plugins in project automation code in Trados 2022 (e.g. by setting some flag that approves unsigned plugins)?

emoji
Parents Reply
  • Hi Jesse,

    the change wasn’t planned or carried out deliberately. Changes to the way Studio works with regard to project automation caused this and we only discovered it when developers posted in here as we don’t do any development work ourselves that use other plugins.

    We do have plans in the future to change a few things that will make life more comfortable for developers but nothing we can give you timelines for at the moment.

    Paul Filkin | RWS

    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

    emoji
Children