tuttle plugins are not available even after preload(False)

[Satheesh Ram]

Hi,

In my centos 7.1 machine, tuttle plugins gets installed to /usr/local/OFX/Plugins and my custom OFX plgins gets installed to /usr/OFX/Plugins folder. I usually softlink the plugin bundle from /usr/local/OFX/Plugins to /usr/OFX/Plugins folder and then those plugins will be visitble via pyTuttle.

But when i switched to v0.12, those soft linked plugins aren't available to python tuttle binding layer

#!/usr/bin/env python

from pyTuttle import tuttle

tuttle.core().getFormatter().setLogLevel_int(1)

tuttle.core().getPluginCache().clearPluginFiles()

tuttle.core().preload(True)

for pl in tuttle.core().getPlugins():

        print pl.getIdentifier()

If I run the above python code, it retuns the plugins installed at /usr/OFX/Plugins folder only.

How do i add /usr/local/OFX/Plugins folder to pyttutle?

[Clément Champetier]

Hello,

Indeed I have just tested it, and it seems that the tuttle host searches plugins recursively in the symbolic link, but the result is not returned by pyTuttle.

I don't see what changes since the v0.12 could produce this...

Maybe one thing if you use the sam command line: are you sure that your custom plugins have a different name and version compared to the tuttle plugins loaded? Because since the v0.12 and the sam tool in python, we do not print duplicates in the following command:

sam do -n

For now, you can indicate your two paths to OFX plugins in the environment variable:

export OFX_PLUGIN_PATH='/usr/local/OFX/Plugins;/usr/OFX/Plugins'

And I used this command to check what are the plugins loaded:

sam do --no-plugin-cache -n

This works on my computer (Fedora 20).

Could you test it?

Regards,

Clement

[Fabien Castan]

How do i add /usr/local/OFX/Plugins folder to pyttutle?

As Clement said, you can add paths to the OFX_PLUGIN_PATH environment variable.

Or you can do it from the API:

tuttle.core().getPluginCache().addDirectoryToPath("/usr/local/OFX/Plugins")