Description: ------------ Config's 'GenericConf' *requires* the newline delimiter to be prefixed by a space. There are many valid configuration files out there that do not use a space. For example, this file will be parse successfully (notice the space preceeding the '\'): 1 keyword:value1, \ 2 value2 while this one will not (notice there's no space preceeding the '\'): 1 keyword:value1,\ 2 value2 Test script: --------------- function demobug() { // if you add a space right before the \\ it will work // otherwise it will fail $configtext= "keyword:value1,\\\nvalue2"; $testfile="testconfig.conf"; $file = fopen ($testfile, "w"); fwrite($file, $configtext); fclose ($file); $c = new Config(); $conf=& $c->parseConfig($testfile, "GenericConf"); echo $conf->toString('GenericConf', $options); } Expected result: ---------------- Should print 'keyword:value1, value2' Actual result: -------------- Prints '[pear_error: message="Syntax error in 'testconfig.conf' at line 2." code=0 mode=return level=notice prefix="" info=""]'

<?php require 'Config.php'; $configtext = array(); $configtext[] = "keyword:value1,\\\nvalue2"; $configtext[] = "keyword:value1, \\\nvalue2"; foreach ($configtext as $n => $data) { $path = dirname(__FILE__) . "bug-12291-" . $n . ".txt"; file_put_contents($path, $data); $c = new Config(); $conf=& $c->parseConfig($path, "GenericConf"); print "Result " . $n . "\n"; print $conf->toString('GenericConf', array()) . "\n"; }

produces ---------- PHP ---------- Result 0 [pear_error: message="Syntax error in 'G:\workbug-12291-0.txt' at line 2." code=0 mode=return level=notice prefix="" info=""] Result 1 keyword:value1, value2 Output completed (0 sec consumed)

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.