diff options
author | Andreas Gohr <andi@splitbrain.org> | 2018-06-01 11:47:32 +0200 |
---|---|---|
committer | Andreas Gohr <andi@splitbrain.org> | 2018-06-01 11:54:18 +0200 |
commit | 4445501665c8c5ed97c7f4e32e93044620181648 (patch) | |
tree | b40d5b0bfb30fdd4675ea175af2e4dbc8af4fa91 /lib/scripts/toolbar.js | |
parent | 2cceef48e0389b650ba7d92055e5b11847651409 (diff) | |
download | dokuwiki-4445501665c8c5ed97c7f4e32e93044620181648.tar.gz dokuwiki-4445501665c8c5ed97c7f4e32e93044620181648.zip |
introduce INFO_DEPRECATION_LOG event
This adds an event to dbg_deprecated(). This allows plugins to handle
deprecation warnings. One example would be @cosmocode/dokuwiki-plugin-sentry
One thing I don't like, but don't know how to avaoid is that this
function used to abort super early when $conf['allowdebug'] wasn't set.
However for the sentry plugin you probably would want logs, but still do
not show any debugging to end users (which allow debug would do).
So now the backtrace is always built, the event triggered and then
everything is sent to dbglog() which may simply throw everything away.
Suggestions on how to improve this welcome.
Diffstat (limited to 'lib/scripts/toolbar.js')
0 files changed, 0 insertions, 0 deletions