Product Overwriting Vbulletin Options with defaults

[Jafo232]

I have a little product my client uses on a bunch of his sites and when I update it to a new version (we develop it in house) and then go and update it, it overwrites all the options for it in the products settings (vbulletin options -> product settings) instead of leaving them in place.

What would cause that? The rest of our in house products do not do this. Our install code is versioned and only creates (does not drop) tables that are unrelated to vboptions. There is no uninstall code.

I am at a bit of a loss what would cause it, but I am assuming there is some product setting that says to replace existing values in a setting group with the default? Any help would be appreciated.

[BirdOPrey5]

In the options settings on the developer installation "vBulletin Default" should be "Yes" and "Blacklist" should be "No." Not sure if that is the issue but I would check those settings first.

[Jafo232]

Yep, that is the way they are set and always are. Never had a need to change them. That does not appear to be it.

[Jafo232]

Anyone?

[BirdOPrey5]

My only other guess would be if there was a plugin on one of the admin_options_* hooks or the validation php code boxes in the mod options actually setting a default value somehow.

[Jafo232]

Thanks. That was actually very helpful, at least it made me look in that direction. This turned out to be a conflict with another product that was saving settings during datastore updates. Thank you so much BirdOPrey5, you made my life a little easier today heh..

[BirdOPrey5]

I aim to please. :up: