Settings variables, not functioning correctly on new mod installs

[mfyvie]

Originally Posted by Dismounted

No, I didn't report it as a bug. No there isn't a function either, but you could possibly call the options file and "save" it.

I took a look at what happens in options.php, right at the end after it checks all the settings it runs build_options(). This function returns the result, and if I print the entire array that it spits out, the correct values are there. When I put this function above my test code, it seems to make no difference, the false values are still reported.

If you (or anyone else) has been able to duplicate this, I'd appreciate it if you could follow the link above to the bug report and click the option to state that you can reproduce the same result.

Initially I flagged this bug as low priority, but after doing further tests I'm convinced that this bug could potentially have harmful effects. What if an admin installed a product where the option reports that something is not public, but in reality, it is (and he never realises).