## Releases

- Apache log4php v2.3.0
- Apache log4php v2.2.1
- Apache log4php v2.2.0
- Apache log4php v2.1.0
- Apache log4php v2.0.0

### Apache log4php v2.3.0

Release date: TBA

JIRA change log

This release introduces various new features and improvements

New features:

- Ability to override the default renderer.
- New appender: FirePHP (thanks to Bruce Ingalls). Still in experimental phase.

Improvements:

- LoggerLayoutPatern has been greatly improved:
  - supports longer conversion words such as `%date` instead of `%d`, `%message` instead of `%m`, etc.
  - added many new conversion words; check out the docs for the full list
  - changed the default conversion pattern to be more verbose
- LoggerAppenderPDO will attempt to reconnect a couple of times if logging fails. This solves the problem with the connection expiring in long running scripts.
- LoggerAppenderDailyFile will rollover even in long running scripts.
- LoggerAppenderMongoDB has improved error reporting

Bugfixes:

- Fixed a bug where upstream loggers would log events regardless of their level.
- Re-enabled usage of PHP constants in config parameters.

Breaking changes:

- LoggerLayoutTTCC has been made deprecated. Please switch to LoggerLayoutPatern.
- Several changes to LoggerAppenderPDO:
  - a database table for logging will no longer be created by the appender; the user must create this table manually.
  - the default date pattern does not include milliseconds (this is faster)
- In LoggerLayoutPattern, it is no longer possible to access $_SERVER and $_ENV values using `%X{server.*}` and `%X{env.*}` conversion words; use the new words `%server{*}` and `%env{*}` instead.
- Custom renderer classes should implement the `LoggerRenderer` interface instead of `LoggerRendererObject`.

Please review the documentation and make any necessary changes to your configuration.

### Apache log4php v2.2.1

Release date: 18.02.2012.

JIRA change log

A bugfix release fixing several critical bugs found since the 2.2.0 release.

Bugfixes:

- Fixed a bug which prevented configuration by passing a LoggerConfigurator instance.
- Fixed a bug which prevented parsing of INI configuration files when using PHP 5.2.x.

New features:

- Added connection timeout parameter to the MongoDB appender.

### Apache log4php v2.2.0

Release date: 20.12.2011.

JIRA change log

New features:

- A new layout: serialized

Improvements:

- Full rewrite of the configuration logic. Makes inline PHP configuration possible.
- Improved error reporting. Warnings will be triggered if problems are detected. This makes locating errors in configuration easier.
- Appenders will use a default layout if no layout is specified in configuration.
- The XML layout has been extended to include MDC data.
- Improved documentation to include more XML and PHP configuration examples.
- New web site appearance (powered by the Bootstrap toolkit).

Breaking changes:

- The socket appender has been rewritten to use a layout. By default it will use the serialized layout.
- The syslog appender has been rewritten and the interpretation of parameters has changed.

Please review the documentation and make any necessary changes to your configuration.

### Apache log4php v2.1.0

Release date: 13.07.2011.

JIRA change log

New features:

- New logging level: TRACE
- New appender: MongoDB (thanks to Vladimir Gorej)

Improvements:

- A lot of bugfixes
- Most of the documentation has been rewritten

### Apache log4php v2.0.0

Release date: 12.12.2009.

JIRA change log

Apache log4php 2.0 is not compatible with the previous versions. Please have the following in mind when upgrading to log4php 2.0 in your project:

- PHP 5.2+ is required
- LoggerManager class has been removed. Use Logger instead.
- LoggerHierarchy is not a singleton anymore by default.
- logs to STDOUT by default
- LOG4PHP_CONFIGURATION constant is no longer used. Please use Logger::configure() to configure log4php.