Shotgun Basic Configuration v1.1.5
What’s new?
We have a new drop-down menu in the login dialog, as well as a number of improved features, such as:
- Polish and bug fixes for Publisher,
- Ability to put all configuration dependencies inside a sub-folder named bundle_cache, and
- Platform improvements around bootstrapping.
Features/Polish
- The login dialog now remembers the list of the 8 most recent sites and users you have used, and displays them. You can also start typing the name of a site or user to filter down the list’s content. [44951]
- The Publish app has a new app setting, enable_manual_load, which defaults to True. When set to False, it no longer shows the ’splash’ screen which lets you load/drag and drop files or browse to them and turns off the drop zone in the left hand side tree view so that items cannot be dropped in there. [46405]
- The tk-multi-demo app now has a context selector widget demo. [46265]
- When using a descriptor-based pipeline configuration, it is now possible to put all its dependencies inside a sub-folder named bundle_cache. It means that you can now store an entire pipeline configuration (hooks, environment and bundles) inside Shotgun so it can be deployed anywhere. [45902]
- When using a descriptor-based pipeline configuration, the contents of the configuration (e.g., tk-config-basic) are no longer copied inside the pipeline configuration, providing a small speed boost and reducing the risk of locked files when updating the pipeline configuration. Those folders will be read directly from where they are stored on disk, i.e., the bundle cache for a shotgun, git, or app_store descriptor, or at the location where path and dev descriptors point to. [40825]
- The path to the log file is now exposed via a log_file property on core Logger objects. [42283]
- Publish with a bad template now has better error handling. [46125]
- The Shotgun utils framework now performs a cached data clean up when it is loaded, only for the sg, sg_nav and thumbs cached folders. Files which have not been modified or accessed in the last 60 days are removed to prevent the cache to grow indefinitely. [39289]
Bugs
- In some circumstances, only the new records added in Shotgun since the previous launch of an app using a ShotgunModel would be added to the model and appear in tree views. This fix ensures that all records always appear in tree views. [45562]
- There were styling issues with Houdini 16+ versions, where some of our style changes bleed into Houdini’s dialogs. This fix ensures our style changes are not bleed into Houdini’s dialogs. [46152]
- The Quick Review app was not working if the playlist status field was missing. This fix ensures that the Quick Review app is no longer looking for the playlist status field. [46459]
- There was an issue which prevented you from configuring the loader in a way so that you would be browsing Versions in the left hand side tree and see the publishes associated with that version. This fix ensures you see the publishes associated with that version. [46438]
- With the Shotgun Standard Integration workflow, the frame range was not set correctly after doing a create read node from Shotgun Panel. This fix ensures that the frame range is always set correctly. [46249]
- With the Photoshop CC standard integration, publishing versioned files always converted publishes to .psd file format. This fix ensures tk-multi-publish2 no longer forces the use of the .psd extension. [42803]
- Sometimes an error was showing up if the .version file was missing. This fix ensures the Photoshop CC extension is now more fault tolerant to a missing .version file. [43699]
- When roaming user profiles were used on a Windows network, using the CEP api to get the path to the extension’s root folder returned the path with any $ characters encoded as %24. This fix ensures that the extension initializes properly. [46396]
- It was not possible to load files having utf-8 encoded names. This fix ensures Loader2 app handles files have utf-8 encoded names correctly. [45167]
- There was a Shotgun Desktop Windows-only issue, where errors raised during bootstrap were not reported to the user. This fix ensures errors are reported successfully. [45989]
- Shotgun picked storages not used by Toolkit when there were multiple storages overlaps in Shotgun. This fix allows Toolkit to specify the storage into which a file needs to be stored. [30005]
- Projects with configurations that used a descriptor without
tank_name
defined sometimes led to bootstrap failure. This fix ensures that no failure happen when a pipeline configuration in Shotgun does not have a tank_name defined. [46590] - Sometimes after a core swap, Shotgun connection objects were created with an older Core API. This fix ensures that the ShotgunUser instantiated with a previous version of the API is re-instantiated with a newer version of the API. [44546]