Component paths in Web UI not getting resolved

2 posts in this topic


I'm having trouble getting ftrack Connect to resolve component paths in the UI.  It's not adding the prefix that I have specified in the custom location I've set up in System Settings.  There are no errors in the ftrack_connect.log file.

A few relevant bits of info:

- Running on Mac OSX

- Using ftrack Connect 1.1.3

- We are using rez for package management.  I am launching ftrack Connect after setting the rez environment by executing "open -a" on the directory, rather than double-clicking on it in the finder.

- I do have a simple custom location plugin specified.  I have a file that is based off this tutorial example:

- The and the custom location code ( are both in the same directory.

- I've set the following environment variables to all point to the directory containing and  FTRACK_CONNECT_PLUGIN_PATH, FTRACK_EVENT_PLUGIN_PATH, FTRACK_LOCATION_PLUGIN_PATH.  (Just trying to keep things simple for now)

I can tell from the log file that the "register" function in is called, it is importing my code successfully and registering that, but the modify_application_launch procedure in is never getting called.  Could there be a problem with the event listener?  My code for subscribing to the event is identical to the example:

def register(session, **kw):
    '''Register plugin to session.'''

    # Validate that session is an instance of ftrack_api.Session. If not,
    # assume that register is being called from an incompatible API
    # and return without doing anything.
    if not isinstance(session, ftrack_api.Session):
        # Exit to avoid registering this plugin again.
        return'Connect plugin discovered.')

    import configure_location

Are there problems with my setup that you can tell from my description?  Where else can I look to find out what is going wrong?

Thanks a bunch!

-- Lori

Share this post

Link to post
Share on other sites

Hi Lori,

if you are using rez,  you can have a look in here for ftrack-connect 1.1.3 package:
The web ui path is resolved through this hook contained in ftrack-connect resources in : 
Add that folder to FTRACK_EVENT_PLUGIN_PATH and PYTHONPATH and you should get your paths resolved.

If you have any issue please let me know.



Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now