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).
安装:
Just copy wp2syslog folder to the wp-content/plugins/ folder
Activate the plugin through the 'Plugins' menu in WordPress
屏幕截图:
更新日志:
1.0.5
fix: compatibility with php 7
sec: better input sanitize
1.0.4
fix: load css only in showlog page
1.0.3
fix: syntax error in table creation
1.0.2
fix: compatibility with php 5.3 (sorry, php -l *php won't work as I expected).
1.0.1
fix: Backward compatibility with php 5.3. Warranty: I've not fully tested with php 5.3.
1.0.0
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
0.2.3
bugfix: error in wp2syslog function (thanks Bobo)
Now is possible to use it in others plugins.
0.2.2
bugfix: typo in event function declaration (thanks Chris)