warting

WIS-Logger let developers to use the “do_action” function to debug theirs plugin.
<h4>Features</h4>
<ul>
<li>Let developers log information/debug/warnings/Errors/Fatal </li>
<li>No need to remove logging after release, if wis-logger is not installed nothing happends </li>
<li>Ability to fetch all kind of PHP errors and log them in the same way</li>
<li>You can shose which debug level you want to log.</li>
</ul>
<h4>Support</h4>
Having problems or need support? Use the feedback button on http://warting.se

WIS-Logger – UDP, File & Growl logger

WIS-Logger is a simple and powerful log system

paniko

To use the custom appenders, add this code in your init plugin for example: Choose among appenders (LoggerAppenderDailyFile, LoggerAppenderRollingFile, LoggerAppenderFile, LoggerAppenderMail, LoggerAppenderMailEvent), for each type you must 
specify the relative parameters, how to official documentation of log4php.
<ul>
<li>
For rolling file appenders:
 ‘1MB’, My_Logger::ROLLING_APPENDER => true, My_Logger::ROLLING_MAX_BACKUP_INDEX => 5 ); $mylogger = My_Logger::get_instance(“”, My_Logger::ROLLING, $parameters); $this->logger = $mylogger->getLogger(); //for debug you add: $this->logger->debug($parameters); $this->logger->debug(“test”); ?></li>
<li>
For mail appender: ”, My_Logger::MAIL_TO => ”, My_Logger::MAIL_SUBJECT => ”, My_Logger::THRESHOLD => My_Logger::LEVEL_DEBUG//6: Sets the root logger level to DEBUG. This means that logging requests with the level lower than DEBUG will not be logged by the root logger. ); 
 $mylogger = My_Logger::get_instance(“”, My_Logger::MAIL, $parameters); ?>
</li>
</ul>
** SET Logger threshold ** A level describes the severity of a logging message. There are six levels, show here in descending order of severity. You can set level of logger, add the parameter:
<ul>
<li>FATAL Highest Very severe error events that will presumably lead the application to abort.</li>
<li>ERROR … Error events that might still allow the application to continue running.</li>
<li>WARN … Potentially harmful situations which still allow the application to continue running.</li>
<li>INFO … Informational messages that highlight the progress of the application at coarse-grained level.</li>
<li>DEBUG … Fine-grained informational events that are most useful to debug an application.</li>
<li>TRACE Lowest Finest-grained informational events.</li>
</ul>
If do you want put a logger in frontend, add this code in template script: ‘1MB’, My_Logger::ROLLING_APPENDER => true, My_Logger::ROLLING_MAX_BACKUP_INDEX => 5, My_Logger::THRESHOLD => My_Logger::LEVEL_DEBUG ); 
 $mylogger = new My_Logger(“”, My_Logger::ROLLING, $parameters); 
 $logger = $mylogger->getLogger(); $logger->debug(“test my logger”); ?>
For more info read the API documents of log4php:<a href="http://logging.apache.org/log4php/docs/appenders.html" title="API Documents" rel="nofollow ugc">Apache Log4php Docs</a>
** Configuration ** You can set configuration path file to export your logger, in the plugin’s settings.

WP MyLogger

This plugin use Apache log4php™ libary for create custom loggers on your file system or mail account. Is possible specify the type (rolling, daily), n …

WIS-Logger – UDP, File & Growl logger vs WP MyLogger