Cross plugin options??

micheall

I've been looking over the documentation and either I've missed it, or it might not be possible.

What I would like to do is get options from one plugin and have it used in another plugin. For instance, setting an admin ID from the common plugin, and then accessing that admin ID option setting via one of the specific zenFBSuite plugins.

Is there an object method not documented or that I've missed that would allow me to do this?

acrylian

You can call any option from anywhere using `getOption()` and also set it using `setOption()`. You can of course even set the same option on all plugins. Then they would overwrite each other so you probably have to make sure that nothing is messed up with that.

sbillard

If you will take a look at the development branch of the SVN you will see an example of how we have handled this. There are options for "shortening" the titles on menus. Since we have three plugins which all do "menu" type things it seemed reasonable that they shared the options.

So look at menu_manager, print_album_menu, and zenpage for how they deal with the "menu_truncate_string" and "menu_truncate_indicator" options.

micheall

Ok, I guess that answers my question indirectly.

What I see from the example of the menu_truncate is that the option itself is substantiated under each plugin, but it's stored under the same name.

I guess my questions is this:
if I've got the option zenFBcommon_appid being handled by the zenFBcommon.php file, can I then use a
`getOption('zenFBcommon_appid');`

from any of the other plugins and have it populate with the data that was entered from the zenFBcommon portion of the plugin?

If using the menu_truncate as an example, it appears that the option is set & handled in each of the plugins that calls for it, which while it works, kind of eliminates the usage of a centralized plugin for the common options that need to be loaded.

sbillard

Actually, the option is not set/handled in more than one plugin. It is displayed in all the plugins, but there is a "master" handler elected for actually changing values. All the "slave" plugins have the changing disabled and provide a link to the master handler.

You should actually visit each plugin's option handling on the admin tabs to see what I mean. It does not work at all to have each plugin actually save the option value as the way plugin options work is that the "apply" button applies for all the plugins.

So, if an option is currently "X" it will have that value in each plugin when the page loads. If you change it to "Y" in the first plugin then apply, the "X" from the second plugin is likely to override the "Y" value.

micheall

Ok, so perhaps I'm missing something simple then...

Looking at print_album_menu, zenpage, and menu_manager; they all handle the plug-in options the same way for menu_truncate stuff. So how is the "master" plug-in selected?

For my current install, for instance, zenpage is the one that makes the changes. But I'm not sure if that's only because I had zenpage loaded first before the other plug-ins were loaded.

micheall

It appears I was just over-thinking the situation as I can use the getOption() without having to set it in the option interface for the slave plugin that would be using it's data.