wp2syslog — Global logging facility for WordPress (WPsyslog revisited)
|Author:||psicosi448 (profile at wordpress.org)|
|WordPress version required:||3.3|
|WordPress version tested:||4.2.1|
|Added to WordPress repository:||17-12-2012|
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|Total downloads:||1 472|
Click to start download
End users can benefit from wp2syslog:
- Log entries for core events help to keep track of the daily business, especially on multiuser blogs.
- Log entries for core events can raise awareness for threats and problems, for example abuse attempts.
- Log entries triggered by plugins allow the user to comprehend the functionality of the plugin.
Developers can benefit in two ways from wp2syslog:
- At each point of the code, a log entry can be triggered. No need to print to the browser, just let wp2syslog put it in the database, and you can have a look later.
- You can develop your plugins with support for wp2syslog. This will give your users the chance to better understand what your plugin is doing (see doc/specs.html).
- fix: load css only in showlog page
- fix: syntax error in table creation
- fix: compatibility with php 5.3 (sorry, php -l *php won’t work as I expected).
- fix: Backward compatibility with php 5.3. Warranty: I’ve not fully tested with php 5.3.
- changes: Refactoring with helping of some phpunit tests.
- changes: The string ident ‘core’, which is added to each wp core message, is changed to more eloquent ‘wpcore’.
- new: added client ip and user-agent to infos logged by default
- bugfix: error in wp2syslog function (thanks Bobo)
Now is possible to use it in others plugins.
- bugfix: typo in event function declaration (thanks Chris)
- fix annoying deprecated function