Download
(2015-05-22, 23:17:14)shawn_a Wrote: looking good, looks like we will have to clean up our config as basic and advanced.
Some of these will wind up being basic configs that need to be in settings, and most are advanced.
3.4 moves everything to global definitions, so there will be 10 times as many settings.
hmmm..
I also need to create a mapping file with id, desc, token, and datatype,version so we can support i18n for our definitions, and auto generate settings inputs from datatypes. I have this basic sorted out in 3.4 but just as basic sections and php comments for now.
Here is an example of new ones in 3.4
https://github.com/GetSimpleCMS/GetSimpleCMS/issues/982
Those look really nice & seem to provide a ton of customization options. If I get it correctly, the constants in
$GS_definitions are the ones this plugin should later integrate? As for $GS_constants, I get why all of them shouldn't be settable after runtime, but I don't get why some of them are not in $GS_definitions, eg. why would you not allow changing GSFILENAMEMAX, GSTITLEMAX, GSDATEFORMAT, GSDATEANDTIMEFORMAT, GSSHOWCODEHINTS in gsconfig.php (or would you allow that in the 'Settings' tab)?
