I'm working on an extension that integrates with the system settings editor. Two of its text fields will always receive a string with the equal-sign character ("=") in it.

When that data is written to localconfig.php, "=" is escaped by its HTML equivalent: "=". Of course, when the extension is called into action, these escaped characters trigger an error because the string is technically malformed.

I could just add str_replace('=', '=', $X) as a pre-processing step in the extension code, but that seems like overkill if there's already a way to retain the "=" characters in localconfig.php.

How it's added to the tl_settings DCA:
Code:
$GLOBALS['TL_DCA']['tl_settings']['fields']['ldapAuth_basedn'] = array (
  'label' => &$GLOBALS['TL_LANG']['tl_settings']['ldapAuth_basedn'],
  'default' => '',
  'exclude' => true,
  'inputType' => 'text',
  'eval' => array('tl_class'=>'w50')
);
How it appears in localconfig (Should read 'DC=ad,DC=acadiau,DC=ca'):
Code:
$GLOBALS['TL_CONFIG']['ldapAuth_basedn'] = 'DC=ad,DC=acadiau,DC=ca';
How it's used in the extension code:
Code:
...
// Search for the TYPOlight user as an LDAP resource
if(($user_search = ldap_search($conn, $GLOBALS['TL_CONFIG']['ldapAuth_basedn'], "(CN=$strUsername)", array('dn'))) !== false) {
...
Thoughts anyone?

--V