Does the Antidote Verifier plugin support the new Antidote 12?

Does the Antidote Verifier plugin support the new Antidote 12? I am using Studio 2021 SR2. I have already asked Druide, the makers of Antidote, but they are deferring to RWS for confirming the plugin compatibility, as Trados AppStore is the author of the plugin.

emoji
Parents Reply
  • Hi Oana, 

    It turns out that the installation of the Antidote Verifier had somehow become corrupted.

    The solution entailed NOT having Trados Studio running and running this program:

    C:\Program Files (x86)\Trados\Plugin installer\Sdl.Community.SdlPluginInstaller.exe

    Run the program at that path and click on the "Uninstall" beside Antidote Verifier.

    Then reinstall the Antidote Verifier from the App Store and click on the green link at the top of the AppStore screen prompting you to restart Trados.

    Upon restart, it is very important to note that the icons for Antidote may appear only on the Add On tab rather than on the Review tab. In my case, I now have to run Antidote 11 from the Add On tab, but that's not a big deal. It works the same way as before.

    Using FreshStart did not solve my problem: without running the above SDL Community SDL Plugin Installer app, I would never have been able to completely uninstall the corrupted version of the plugin and regain my critical access to Antidote 11

    Ian Rahn

    emoji
Children
  •   

    I want to acknowledge the concerns raised about Antidote V12 and Trados Studio 2024 compatibility. There have been some posts in the RWS Community and on social media, but I want to be clear—we don’t yet have enough concrete evidence to confirm that V12 is NOT incompatible with Studio 2024.

    As an app provider, we’ve reached out to Druide, and neither of us is aware of specific reasons why issues are being reported. That said, I take this seriously and want to get to the bottom of it.

    I know some of you have reported crashes and errors, and I’ve seen mentions of a "corrupt plugin" and cases where refreshing Studio seemed to help. However, these posts don’t provide the detailed data we need to investigate properly, nor do they confirm whether refreshing the installation paths actually resolved the issue.

    Right now, we need screenshots of the errors and, more importantly, the log file from:
    Open file folder C:\Users]\AppData\Roaming\Trados AppStore\AntidoteVerifier\Logs

    If you’re experiencing issues, please share this information—it’s the only way we can analyse what’s happening at a code level. We’ve also got an open dev item for this: SDLCOM-6447, which will be assigned as soon as we have enough data to move forward.

    I completely understand the frustration and want to reassure you that this isn’t being ignored. We just need the right information to investigate properly.

    Thanks for your help!

    Lyds

    Lydia Simplicio | 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

    emoji