PEAR Bug Search Results

Config: Feature/Change Request 16724 [Open] PHPConstants container should have option lowercase

lars at legestue dot net — 2009-10-22T08:07:35+00:00

Config Feature/Change Request
Reported by lsolesen
2009-10-22T08:07:35+00:00
PHP: 5.2.5 OS: ubuntu Package Version: 1.10.11

Description:
------------
It should be possible to get keys of the array from the PHPConstants container in lowercase.

Config: Feature/Change Request 16656 [Open] New 'linebreak' option for IniCommented container

wiesemann at php dot net — 2009-09-29T10:09:36+00:00

Config Feature/Change Request
Reported by wiesemann
2009-09-29T09:42:11+00:00
PHP: Irrelevant OS:  Package Version: 1.10.11

Description:
------------
The attached patch adds a new 'linebreak' option (default value: "\n") to the IniCommented container.

The patch also adds error handling for a failure of the file() call.

Config: Bug 16590 [Open] parseConfig phparray ignores named arrays that use numbers as name

pear at kitik1 dot com — 2009-09-10T15:48:18+00:00

Config Bug
Reported by circalucid
2009-09-10T15:42:09+00:00
PHP: 5.2.5 OS: Ubuntu 9.04 Package Version: 1.10.11

Description:
------------
I'm not entirely sure this is a bug or an intended behavior in PHP but when I create an array and assign a number as the first element's name, I get a sequential array after passing this array to parseConfig. If the first element is a string, everything works kosher whether any of the following names are a string or number.

I'm using a workaround prefix but is this a bug?

Test script:
---------------
 array(
        '203' => 'mysql',
        'host' => 'localhost',
        'user' => 'root',
        'pass' => 'root'
     )
  );
  $conf2 = array('root' => $conf2);
  print_r($conf2['root']['DB']);
  
  $c = new Config();
  $arr_read =& $c->parseConfig($conf2['root'],'phparray');
  $arr_read = $arr_read->toArray();
  if (PEAR::isError($arr_read)){die('Dote'."\n");}
  print_r($arr_read['root']['DB']);
  unset($arr_read);
?>

Expected result:
----------------
Array
(
    [203] => mysql
    [host] => localhost
    [user] => root
    [pass] => root
)
Array
(
    [0] => mysql
    [1] => localhost
    [2] => root
    [3] => root
)


Actual result:
--------------
Array
(
    [203] => mysql
    [host] => localhost
    [user] => root
    [pass] => root
)
Array
(
    [203] => mysql
    [host] => localhost
    [user] => root
    [pass] => root
)

Config: Bug 15964 [Verified] errors in test suite

bjohnson80498 at gmail dot com — 2009-08-25T06:56:02+00:00

Config Bug
Reported by bjohnson
2009-03-01T17:03:23+00:00
PHP: 5.2.8 OS: Linux/Fedora Package Version: 

Description:
------------
      # pear run-tests -p Config
Running 16 tests
...
FAIL [ 3/16] test for bug 3051[/usr/share/pear/test/Config/test/bug3051.phpt]
...
FAIL [16/16] regression test for bug
#10185[/usr/share/pear/test/Config/test/bug10185.phpt]
wrote log to "/root/run-tests.log"
TOTAL TIME: 00:01
14 PASSED TESTS
0 SKIPPED TESTS
2 FAILED TESTS:
/usr/share/pear/test/Config/test/bug3051.phpt
/usr/share/pear/test/Config/test/bug10185.phpt

Test script:
---------------
      

Expected result:
----------------
      

Actual result:
--------------
   no failure when running test suite

Config: Feature/Change Request 13791 [Open] Options for the PHPConstants container

lu dot corbo at gmail dot com — 2008-04-28T12:45:28+00:00

Config Feature/Change Request
Reported by lucor
2008-04-28T12:45:28+00:00
PHP: Irrelevant OS: Irrilevant Package Version: CVS

Description:
------------
It could be useful to set via options the possibility to add a comment and use double quote instead of single quote.
In attach a patch allows this passing the following options to the writeConfig method:
- use_double_quote = true -> enable the double quote;
- comment = some text -> add a custom comment.

Config: Bug 13116 [Verified] Syntax Strict notice for references on constructors

despoix at openxtrem dot com — 2008-05-14T07:50:37+00:00

Config Bug
Reported by tomdesp
2008-02-13T13:03:01+00:00
PHP: 5.1.6 OS: all Package Version: 1.10.11

Description:
------------
Config constructor will try to to reference a container after new construction, thus will throw a E_STRICT error in PHP5.

Let's recall it has no effect and is deprecated. Code should be updated as all other major packages have already been on this point.

Test script:
---------------


Actual result:
--------------
Strict standards: Assigning the return value of new by reference is deprecated in c:\wamp\php\PEAR\Config.php on line 80

Strict standards: Assigning the return value of new by reference is deprecated in c:\wamp\php\PEAR\Config.php on line 166

Strict standards: Assigning the return value of new by reference is deprecated in c:\wamp\php\PEAR\Config\Container.php on line 111

Config: Bug 12388 [Open] GenericConf doesn't allow whitepace to left of directive delimiter

pear at j9ac9k dot info — 2007-11-06T00:04:16+00:00

Config Bug
Reported by paleozogt
2007-11-06T00:04:16+00:00
PHP: 4.4.7 OS: irrelevant Package Version: 1.10.11

Description:
------------
GenericConf doesn't allow whitespace to the left of the directive delimiter (the 'equals' option).

For example, this is valid:
  keyword:     value
but this is not
  keyword :value

The regex used in GenericConf allows for any amount of whitespace to the *right* of the delimiter ("\s*") but doesn't allow for any on the *left* side of the delimiter.

Test script:
---------------
function demobug() {
   // this will fail unless you remove the 
   // space to the left of the colon
   $configtext= "keyword : value";

   $testfile="/tmp/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:
----------------
It should display "keyword:value".


Actual result:
--------------
Instead it displays, "[pear_error: message="Syntax error in '/tmp/testconfig.conf' at line 1." code=0 mode=return level=notice prefix="" info=""]"

Config: Bug 12387 [Open] GenericConf doesn't allow for hyphens on left-hand-side of a directive

pear at j9ac9k dot info — 2007-11-05T23:53:08+00:00

Config Bug
Reported by paleozogt
2007-11-05T23:53:08+00:00
PHP: 4.4.7 OS: irrelavent Package Version: 1.10.11

Description:
------------
The GenericConf format doesn't allow hyphens on the LHS of a directive.  For example, this is valid:
  key_word:value
but this is not
  key-word:value

The underscore is allowed because the regexp used is "\w", which includes alphanumeric and underscores.  To support hyphen, a hyphen must be explicitly included in the regexp.


Test script:
---------------
function demobug() {
   // this will fail unless you remove the hyphen
   $configtext= "key-word:value";

   $testfile="/tmp/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:
----------------
it should display, "keyword:value"

Actual result:
--------------
it displays, "[pear_error: message="Syntax error in '/tmp/testconfig.conf' at line 1." code=0 mode=return level=notice prefix="" info=""]"

Config: Bug 12291 [Verified] PEAR GenericConf newline shouldn't need a space

pear at j9ac9k dot info — 2008-05-14T07:44:05+00:00

Config Bug
Reported by paleozogt
2007-10-22T03:38:55+00:00
PHP: 4.4.7 OS:  Package Version: 1.10.11

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=""]'

Config: Feature/Change Request 11827 [Open] notice when using arrays (directive[]=value) in inifiles

theend at life dot pl — 2007-08-13T02:38:58+00:00

Config Feature/Change Request
Reported by mad
2007-08-13T02:38:58+00:00
PHP: 5.1.6 OS: linux gentoo Package Version: 1.10.11

Description:
------------
When you are using iniFile which looks like

[section]
directive[] = value1
directive[] = value2

Its correctly parsed as an array
array( 'section' => array( 'directive' => array( value1, value2 ) ) )

But there are some notices about converting array to string.