Relating to the obsolete comment.  We have a core/obsolete.php file which makes sure that the admin is not using any configs that are obsolete and not effective.  This is to get the admin to change them to get the appropriate behavior.  There is two ways to obsolete a variable:
obsolete( 'ldap_port' );  // marks a config as obsolete.
obsolete( 'ldap_port', 'ldap_uri' ); // marks ldap_port as obsolete, and instructs the admin to use ldap_uri instead.
I don't have access to the code right now, so the above is from memory.
On Mon, Mar 28, 2011 at 7:54 AM, Damien Regad <> wrote:
Thank you both for your quick feedback.

 > On Mar 28, 2011, at 5:51 AM, Paul Richards wrote:
 >> Basically, the ldap_port stuff should be removed.

By the way, I think it's an excellent idea to implement an array of LDAP
servers and indeed in this case it makes no sense to have the port
stored separately.

On 28.03.2011 16:27, Victor Gmail wrote:
> I'm ok with deprecating the port as long as there is clear documentation
> in config_defaults_inc.php and the manual.

Your word is my command :-)
I will make sure that the 1.3.x config_defaults_inc.php and docbook
contain the required info and submit a patch.

> The check for obsolete configs should point to the uri as the replacement.

I'm not sure what you mean by that. Can you please clarify ?


Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
mantisbt-dev mailing list