Message-ID: <2089008740.4372.1485866310309.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4371_99023070.1485866310309" ------=_Part_4371_99023070.1485866310309 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
eZ Publish 5.1 includes a logging mechanism for debugging purposes in de= velopment environments, which monitors Stash, introduced in Stash-bundle, and the persistence cache mechanism.
Logging is enabled by default, except for the production environment to = avoid excessive memory usage on production environments.
StashBundle logging, represented by the stash.logging
setti=
ng, and persistence cache logging, represented by the setting paramet=
ers.ezpublish.spi.persistence.cache.persistenceLogger.enableCallLogging, and are both enabled by default on development environments.
Both s=
ettings expect a boolean value (true
or false
), s=
o, if you desire to turn off the logging mechanism you can use the followin=
g configuration in ezpublish_dev.yml
:
stash: logging: false caches: default: handlers: - FileSystem inMemory: false registerDoctrineAdapter: false parameters: ezpublish.spi.persistence.cache.persistenceLogger.enableCallLogging: fa= lse=20
Be aware that using stash logging and persistence cache logging will req= uire additional memory. This should be used for debugging purposes only.