Timofey Penkov Posted October 16, 2018 Report Share Posted October 16, 2018 Hey there! Please, tell me how i can delete all custom created Actions? I've practiced with tutorial phyton scripts and get a bit of mess in my ftrack actions. Thanks! Link to comment Share on other sites More sharing options...
Lorenzo Angeli Posted October 17, 2018 Report Share Posted October 17, 2018 Hi Timofey, if you are using connect, click on the system tray icon and then Open plugin directory. in there you should be having the actions code, removing or moving it to another folder should resolve your issue. if you have any issue know ! L. Link to comment Share on other sites More sharing options...
Timofey Penkov Posted October 18, 2018 Author Report Share Posted October 18, 2018 Thanks! Link to comment Share on other sites More sharing options...
dthomlison Posted October 30, 2018 Report Share Posted October 30, 2018 What if we did not use Connect? How does one remove custom actions? Link to comment Share on other sites More sharing options...
Lorenzo Angeli Posted November 1, 2018 Report Share Posted November 1, 2018 Hi @dthomlison depending on your operating system the folder containing the actions, could be in different places: OS X: ~/Library/Application Support/ftrack-connect-plugins Windows: C:\Documents and Settings\<User>\Application Data\Local Settings\ftrack\ftrack-connect-plugins Linux: ~/.local/share/ftrack-connect-plugins get to the folder , depending on your Os , and remove the actions. if you are still having issues please let us know. Cheers. L. Link to comment Share on other sites More sharing options...
dthomlison Posted November 1, 2018 Report Share Posted November 1, 2018 thanks, I found out that the action was still showing because the python script was still running and I guess the session was still active. Killing the python process removed the action from our ftrack. Link to comment Share on other sites More sharing options...
Martin Pengelly-Phillips Posted November 4, 2018 Report Share Posted November 4, 2018 We extended ftrack to automatically add fqdn and pid to the subscriber information when subscribing to events, along with an `EventHub.subscribers_for(event)` method. With those we can easily find any rogue event listeners and shut them down. Might be something for ftrack to add to the core? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.