You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4php-dev@logging.apache.org by "Ivan Habunek (Created) (JIRA)" <ji...@apache.org> on 2012/01/28 13:03:10 UTC
[jira] [Created] (LOG4PHP-167) INI configuration files not parse
when using PHP 5.2.x
INI configuration files not parse when using PHP 5.2.x
------------------------------------------------------
Key: LOG4PHP-167
URL: https://issues.apache.org/jira/browse/LOG4PHP-167
Project: Log4php
Issue Type: Bug
Components: Code
Affects Versions: 2.2
Environment: PHP 5.2.x
Reporter: Ivan Habunek
Assignee: Ivan Habunek
Priority: Critical
LoggerConfigurationAdapterINI uses INI_SCANNER_RAW option when calling parse_ini_file().
This option was introduced in PHP 5.3. and the result is that parsing of INI config files failes when using php 5.2.x.
To keep backward compatibility, this option should be removed. Special care should be taken that option parsing is not affected. Especially since parse_ini_file() without the RAW option produces some unexpected results (check LoggerOptionConverter).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (LOG4PHP-167) INI configuration files not parse
when using PHP 5.2.x
Posted by "Ivan Habunek (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4PHP-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Habunek updated LOG4PHP-167:
---------------------------------
Fix Version/s: 2.2.1
> INI configuration files not parse when using PHP 5.2.x
> ------------------------------------------------------
>
> Key: LOG4PHP-167
> URL: https://issues.apache.org/jira/browse/LOG4PHP-167
> Project: Log4php
> Issue Type: Bug
> Components: Code
> Affects Versions: 2.2.0
> Environment: PHP 5.2.x
> Reporter: Ivan Habunek
> Assignee: Ivan Habunek
> Priority: Critical
> Fix For: 2.2.1
>
>
> LoggerConfigurationAdapterINI uses INI_SCANNER_RAW option when calling parse_ini_file().
> This option was introduced in PHP 5.3. and the result is that parsing of INI config files failes when using php 5.2.x.
> To keep backward compatibility, this option should be removed. Special care should be taken that option parsing is not affected. Especially since parse_ini_file() without the RAW option produces some unexpected results (check LoggerOptionConverter).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (LOG4PHP-167) INI configuration files not parse
when using PHP 5.2.x
Posted by "Ivan Habunek (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4PHP-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Habunek resolved LOG4PHP-167.
----------------------------------
Resolution: Fixed
> INI configuration files not parse when using PHP 5.2.x
> ------------------------------------------------------
>
> Key: LOG4PHP-167
> URL: https://issues.apache.org/jira/browse/LOG4PHP-167
> Project: Log4php
> Issue Type: Bug
> Components: Code
> Affects Versions: 2.2.0
> Environment: PHP 5.2.x
> Reporter: Ivan Habunek
> Assignee: Ivan Habunek
> Priority: Critical
> Fix For: 2.2.1
>
>
> LoggerConfigurationAdapterINI uses INI_SCANNER_RAW option when calling parse_ini_file().
> This option was introduced in PHP 5.3. and the result is that parsing of INI config files failes when using php 5.2.x.
> To keep backward compatibility, this option should be removed. Special care should be taken that option parsing is not affected. Especially since parse_ini_file() without the RAW option produces some unexpected results (check LoggerOptionConverter).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira