After having upgraded from Studio 2017 to 2019 I am no longer able to work with StarTransit Packages in Studio. I have installed the plugin "TransitPackage Handler" for Studio 2019 which worked perfectly with Studio 2017. Now, in Studio 2019, I can open the package (defining details such as location, template etc.), but when the package has been opened/created in Studio, the files have not and cannot be prepared for translation (error message under "Convert to translateable format": "Object reference not set to an instance of an object").I have installed the latest SP1, I have tried to de- and reinstall Studio (and, of course, the plug-in), but to no avail. The file format of the Transit package is .PPF. I have tried importing/opening older Transit packages which worked well under Studio 2017, but that is not possible either. I can, however, still access my older projects which were first imported/opened under Studio 2017, and it is possible to create new return packages for those older projects as well.Has anybody experienced a similar problem and found a solution? Any help will be appreciated - thanks a lot in advance!
Hello Susanne Rosenberg ,
Can you confirm you have the latest version of the app installed please-
You can also check via the SDL Plugin Management tool
If everything is up to date and it still does not work, would you be able to share the package (firstname.lastname@example.org) with us, so we can test this please?
Hi Susanne Rosenberg
All the best,
I am trying to do this in Studio 2019, but I don't have a project template, which is apparent rquired:
Where can I get a project template from if all I have is the .PPF file?Am I right in thinking that the Location can simply be any empty folder?
It would be REALLY helpful if the tooltip with the message "Template is rquired" could not only be corrected, but also put in a more sensible position so that "Default" isn't obscured!
David, basically you can choose any Studio template with the language combination in matter (including the standard Studio template) - and you can always add extra TMs etc. in the project settings afterwards. Or you can set up a Studio template especially for this kind of projects.I should, however, mention that the solution I found did not work in the long run, so now I have chosen to use Studio 2017 for Transit projects since the app (TransitPackage Handler) works perfectly in this version. I only have to deal with Transit packages from one customer and do not need to update my 2019 TMs with the content, otherwise this solution would require some extra work for TM exports and imports. Good luck!