I am currently coding the product version of this source code hack. I will soon post my .zip here for Derek.

Good job Floris :)

Upgrade instructions:
uninstall the source code hack and follow install instructions.

Install instructions:
Add this as a new product, import the .xml

Screenshot:
Here.

I am sure someone knows how to make a query that works, but I have too little time right now to try things out on a fresh install.

Basicly, if you want this right now and don't want to wait for someone to update the product .xml with install/uninstall query & settings turn on debug code and go to the vbulletion options > admincp options > and click on 'add a new setting', and fill it in like the below screenshot.

Then import the .xml from this .zip which is ready for the switch 1/0

I am sure kirby knows ;)

Hmm ... what should I know? :)
Don't really understand what you were talking about queries, sorry.
This Hack does not seem to need any install/uninstall codes?

Also, I think that a setting to turn this featurs On/Off is redundant - one could just activate/deactivate the product?

Then we'll leave the on/off option out.

But to teach derek and others, what would those queries be?

Which queries, for the setting?
None at all - Product Management does take care of it :)

One would only have to wrap the Code in
But as said, that just seems to be redundant ;)

Yes, whatever you think if it is redundant or not is not the point here. I am just trying to understand how the product.xml will look if we would want a vbulletin options setting for the group admincp - the code you gave won't make a magic option appear out of thin air in the admin option group. How does it get there? the product.xml only has means like this:

<settinggroup name="admincp" displayorder="200">
<setting varname="use_quick_web_search" displayorder="60">
<datatype>free</datatype>
<defaultvalue>1</defaultvalue>
</setting>
</settinggroup>

but that is just telling it what to use.. it still won't generate the option, why ? .. because you dont tell it what the title or description would be for example.. or where it stores a value, what value, etc..

For that, a query has to be run, like shown on the screenshot you can enter that manually with running in debug, add setting .. but the product can have this in the <code> part for install & uninstall code. That's the query I am trying to understand how to figure that out.

Adding the setting in the admincp through debug and then going to the product > export > .. won't make that appear in the .xml

Floris, the product XML you posted here contains everything to make the setting appear.
All settings are stored in table setting, column value - each setting is identified by its Varname.
Title and Description are just Phrases, and those are in the Product XML as well.

So I don't really understand what you are talking about queries?

Also, please don't get me wrong on the redundant stuff.
I didn't want to argue, I just wanted to point this out, as others might not think of the possibility to just disable the product.

So when you import the product, the acp > vboptions >vboptions > admincp options > has a new option with exactly the settings like in the screenshot? https://vborg.vbsupport.ru/attachmen...chmentid=34808 ?