keyframe Posted July 25, 2017 Report Share Posted July 25, 2017 Hello everyone, Please bear with me -- i'm trying to wrap my head around several key ftrack concepts and [obviously] missing a few key bits of info. We are running a local install, version 3.3.41, our apps are centrally installed, and our shell environments are set using rez-env. I'm attempting to get the connectors (starting with ftrack_connect_nuke) to publish to a custom location, which I've registered via a location plugin: import ftrack locs = ftrack.getLocations() for loc in locs: print loc.getName() + " : " + str(loc.getPriority()) results in: ae.toronto.gene_dump : 1 ftrack.unmanaged : 90 ftrack.connect : 95 ftrack.review : 110 ftrack.server : 150 Which leads me to believe that my location is configured correctly. i'm using a ClassicStructure(), and a DiskAccessor with a prefix that I have perms to write into. I also have a custom resolver, which appears to be running correctly (or at least that's what the local diagnostics page claims). For some reason -- no joy. every attempted publish ends up in ftrack.origin (which doesn't appear in the locations list, myseriously). Am I missing something obvious? Cheers, G Link to comment Share on other sites More sharing options...
Mattias Lagergren Posted July 26, 2017 Report Share Posted July 26, 2017 Hi, when you publish is it from the nuke plugin or with custom code? The origin location is the first location where a component ends up when you create. Then the idea is that it should be moved to another persistent location. Link to comment Share on other sites More sharing options...
keyframe Posted July 26, 2017 Author Report Share Posted July 26, 2017 Heya Mattias, I'm attempting to publish from the ftrack_connect_nuke plugin to a location with the lowest priority. Am I barking up the wrong tree? G Link to comment Share on other sites More sharing options...
keyframe Posted July 26, 2017 Author Report Share Posted July 26, 2017 Ug, Is it possible that 0.6.2 versioned connectors need a non-legacy location plugin? http://ftrack.rtd.ftrack.com/en/latest/developing/locations/index.html seems to imply otherwise... and contradics this post: http://forum.ftrack.com/index.php?/topic/941-ftrack-connect-version-062/ I must admit -- there is a lot of documentation -- but it's really really challenging to know where to look for relevant/up to date info. G Link to comment Share on other sites More sharing options...
Mattias Lagergren Posted July 27, 2017 Report Share Posted July 27, 2017 Quote I'm attempting to publish from the ftrack_connect_nuke plugin to a location with the lowest priority. Am I barking up the wrong tree? I think you're heading in the right direction and that we can get this to work for you. Quote http://ftrack.rtd.ftrack.com/en/latest/developing/locations/index.html seems to imply otherwise... and contradics this post: http://forum.ftrack.com/index.php?/topic/941-ftrack-connect-version-062/ This is unfortunate and the documentation that you link to will be updated soon. The forum post is the accurate one. 19 hours ago, keyframe said: I must admit -- there is a lot of documentation -- but it's really really challenging to know where to look for relevant/up to date info. We are aware of this and will start refreshing the docs after the summer - to clarify and make it more centralised with more guides etc. Link to comment Share on other sites More sharing options...
Mattias Lagergren Posted July 27, 2017 Report Share Posted July 27, 2017 Quote Ug, Is it possible that 0.6.2 versioned connectors need a non-legacy location plugin? To answer your original question, the 0.6.2 integrations is using locations from the new api. There is a compatibility layer that will proxy legacy locations to the new api: https://bitbucket.org/ftrack/ftrack-location-compatibility/ - but if it is not a lot of extra work I would recommend rewriting your locations in the new api. Sorry for the inconvenience. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.