Marta Masłowska

To uninstall these plugins use the windows control panel:

But I'd still recommend you delete your plugin folders in case you have others that were affected.  CU8 broke a few things that needed to be updated later :-(

Hi Paul,

so I updated Studio again (SR2 16.2.8.9097) and a similar thing happened... (see screenshot). How do I fix Studio so that I can  use the TM upgrade option again? Issues with every update are very disruptive

Thanks and I look forward to your suggestions.

Marta

Marta Masłowska

I think you need to close Studio, then remove the "Trados Compatibility and Migration Power Pack".  Once removed download and install the latest one from the appstore.

Thank you Paul, it worked again! is there any way this could be fixed for future updates? It's not great to have to delete and reinstall this component every time.

Thank you and have a nice afternoon.

Marta Masłowska

Marta Masłowska said:

is there any way this could be fixed for future updates?

The problem is twofold:

1. the core product (Trads Studio) changed enough with this update that a new version of the app was required
2. the core product doesn't handle non-conforming plugins well

The first one will ideally not happen at all unless we are moving from a major release to another major release.  But unfortunately the recent minor updates have all included some important, but breaking changes.  Hopefully in the future this won't happen so often, if at all.

The second one... I know the core development team have taken this problem very seriously and are looking at the best ways to manage this in the future.  So if we do get breaking changes we should, for example, not load a non-conforming plugin at all.  Then at least Studio will run and you'll just have to make sure you read the release notes and take the appropriate action to install any required updates.

Apologies for the inconvenience this caused you... these sort of things really are the last thing we want to see too!

Marta Masłowska

Marta Masłowska said:

is there any way this could be fixed for future updates?

The problem is twofold:

1. the core product (Trads Studio) changed enough with this update that a new version of the app was required
2. the core product doesn't handle non-conforming plugins well

The first one will ideally not happen at all unless we are moving from a major release to another major release.  But unfortunately the recent minor updates have all included some important, but breaking changes.  Hopefully in the future this won't happen so often, if at all.

The second one... I know the core development team have taken this problem very seriously and are looking at the best ways to manage this in the future.  So if we do get breaking changes we should, for example, not load a non-conforming plugin at all.  Then at least Studio will run and you'll just have to make sure you read the release notes and take the appropriate action to install any required updates.

Apologies for the inconvenience this caused you... these sort of things really are the last thing we want to see too!

Does the App store integration get called at startup to check for app upgrades? If not, it may be an idea. It could even scan for blocked apps due to breaking changes and disable them.

David Watson

David Watson said:

Does the App store integration get called at startup to check for app upgrades?

Yes it does.

David Watson said:

It could even scan for blocked apps due to breaking changes and disable them.

This is exactly the sort of solution the team is looking at :-)