Developer

Page tree

translate5 provides a flexible way of switching debug output.

In installation.ini debugging can be enabled for different parts of the software. Example, to enable SegmentStatistics debugging add the following parameter to your installation.ini:

  runtimeOptions.debug.plugin.SegmentStatistics = 1

The parameter is dynamic, that means to can also enable debugging for all plugins:

  runtimeOptions.debug.plugin = 1


What for debug output is produced, depends on the plugin or section you have enabled. Normally the debug output is written directly to PHP error log.

The value set value is compared binary, for some sections more debugging can be enabled.

An complete list of available debug parameters is currently not available, the following are only a few examples:

  runtimeOptions.debug.plugin.transit = 1 ; for extended mismatch output and extended output on import errors
  runtimeOptions.debug.plugin.transit = 3 ;&2 for TransitInfoFields
  runtimeOptions.debug.plugin.transit = 7 ;&4 for strict mode in mismatch output
  runtimeOptions.debug.plugin.TermTagger = 1
  runtimeOptions.debug.plugin.SegmentStatistics = 1
  runtimeOptions.debug.plugin.ArchiveTaskBeforeDelete = 1

HTTP Request debugging

All HTTP Request implementations using the Zend_Http_Client instanced via ZfExtended_Factory::get can be easily debugged:

just set in the installation.ini

debug.httpclient = 1

or to a string to filter the logged URLs. This example would log only requests to OpenTM2.

debug.httpclient = otmmemory

If enabled the content transfered to and from an external HTTP Service is then logged to the PHP error log

  • No labels