Documentation of possible values in constants.php and conf_global.php?

[TSP]

I'm wondering if you have any documentation on all the possible values that can be defined in conf_global.php and / or constants.php?

I guess initdata.php pretty much serves as a "full documentation" on all the official values to be possible to define in constants.php, but conf_global.php seems to not be documented in any way.

And is there some values that can be defined in constants.php but are not mentioned in initdata.php?

[bfarber]

@TSP - there are a handful of constants that could in theory be defined in constants.php, but it's not "easy" to document. Basically any constant anywhere in the suite that is defined, and has a if( !defined() ) check first. For instance, the IP.Content FURL marker could be defined in constants.php.

The only conf_global.php variables that aren't already in the file are the power-user settings which are defined at the top of admin/sources/base/core.php, and the alternate cache store engine variables (those are documented).

[Rimi]

The only conf_global.php variables that aren't already in the file are the power-user settings which are defined at the top of admin/sources/base/core.php,

Actually, the setting that enables/disables status updates entirely and also the settings that limits the maximum amount of characters for status updates and subsequent replies are not listed here, yet when you add them to the conf_global.php file they work as intended.

$INFO['su_enabled']

$INFO['su_max_chars']

There is also one for

$INFO['fake_mail']

when testing email. So really a documentation for all the variables that can go here would be nice, but I can see how it'd be tedious. Still, these are all useful settings.

[bfarber]

If you want to compile a list of any others, I'll post something soon in the documentation. I'm not sure when I'll have time to try to hunt down through the source all of these settings (it's not an easy task as you can imagine).

[Rimi]

Those are actually the only ones that I've run across myself (because I had a personal need for them). I think there are a couple more status update related ones. su_max_replies is one.. Isn't there one for HTTPS?

Yeah, it's definitely going to be a hassle to find them all. But the status update ones are pretty important since I've had to tell people about them on a handful of occasions. It may even be ok to just add them as ACP settings.

[Rimi]

Actually I don't know if it's worth doing a documentation for conf_global values. I think it's better to have a doc on the fake email setting (since it requires setting up a new directory) and perhaps one on the management of status updates if you don't add them as actual acp settings.

Don't know if this was mentioned but ip.content database page titles might as well also be included even though they have a doc all to themselves. Really depends on how you choose to handle this.

[TSP]

Those are actually the only ones that I've run across myself (because I had a personal need for them). I think there are a couple more status update related ones. su_max_replies is one.. Isn't there one for HTTPS?

If there is a power setting that can override the ACP setting for https then I would really like to know about it!

As per my feedback/suggestion in this post:

[bfarber]

Actually I don't know if it's worth doing a documentation for conf_global values. I think it's better to have a doc on the fake email setting (since it requires setting up a new directory) and perhaps one on the management of status updates if you don't add them as actual acp settings.

Don't know if this was mentioned but ip.content database page titles might as well also be included even though they have a doc all to themselves. Really depends on how you choose to handle this.

Already documented here: http://community.invisionpower.com/resources/guides.html/_/advanced-and-developers/api-methods/sending-emails-r183

[Rimi]

Oh right. So then the only real thing I found was the status update settings.