Quote:
Originally Posted by KirbyDE
Which queries, for the setting?
None at all - Product Management does take care of it
One would only have to wrap the Code in
PHP Code:
if ($vbulletin->options['use_web_search'])
{
// Code here
}
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