Using the same $vbulletin->options across multiple products

[DetroitYES]

So, I have two products, each of which offer to make a call to bit.ly to shorten a url before tweeting to a twitter account.

For me, it would be most sensible if I could utilize the same vbulletin option in both products, rather than having to enter the same api keys twice for each.

I've noticed that $vbulletin->options seem to be independent of any product aside from existing in the products installation xml file.

Is it valid/ would there be a problem with having the code to create the same option across multiple products? -- this is assuming that they were listed under the same setting group, and same var name in each xml file for the two products?

What I'm trying to move towards is a central framework for all of my products to simplify managment.

So in abstract, lets say i have product A: atdasd & B: atdsbr and I would like to combine their common elements under the prefix atdatd...

Thanks.

[Boofo]

You could do it if you just require the mod that has the option for the second mod.

[cellarius]

If the option already exists, it will simply be ignored on install.

[DetroitYES]

If the option already exists, it will simply be ignored on install.

Thank you, that is what I assumed but wanted to confirm.

[Adrian Schneider]

Build a product for each unique functionality that you can isolate. Make your own products dependent on it (literally add it as a dependency).

cellarius, are duplicates ignored or removed when you uninstall one of them?

[cellarius]

I'd have to check, but they would probably be uninstalled. That's a catch, indeed. YouÄre suggestion with seperate products per function is likely the way to go.

[DetroitYES]

are duplicates ignored or removed when you uninstall one of them?.

oh, man good point...