remove unnecessary printing DOKU_LF

split longer show() into task methods.

The structure of Ui\Revisions is similar to Ui\Recent. Ui\Revisions::getRevisions() returns a arrey of rev info array as same as getRecent().

more narrow jQuery selector to rev2[] checkbox

This fix enables to use disabled checkbox for non-existing revision page or media file in the HTML form of Ui\Revisions.

Optimized pageRestoreConfirm function

Tests for Portuguese and Spanish

Collations for Portuguese and Spanish; examples for Portuguese; better comments

Changes according to revisions in https://github.com/moisesbr-dw/dokuwiki/pull/2

Many minor details and use of Sort::xyz() instead of intl_xyz() in files outside the "inc" folder.

shorten Ui\Recent::show(), split out sub methods

Requrie *PHP7*, using anonymous class in Ui\Recent::getObjRevInfo()

fixed plugin name output on load error

added logging configuration

Log facitlities can now be disabled. By default only debug is disabled.
It might make sense to by default disable deprecated as well?

Debug logging is now independend of

added logging configuration

Log facitlities can now be disabled. By default only debug is disabled.
It might make sense to by default disable deprecated as well?

Debug logging is now independend of the allowdebug method. allowdebug
was often used in two ways: for displaying errors directly to the user
and for logging to the debug log. Now it only controls the former.

show more ...

replaced out calls to dbglog with new Logger calls

added convenience methods to log to our default facilities

added logviwer admin plugin

This allows for easy viewing of the available logs.

The log format was sligthly adjusted again for easier parsing.

adjust callstack depth for deprecation message further

added log dir to git

better deprecation messages for self required plugin base files

central logging mechanism

This introduces a logger mechanism and a new data/log directory. This is
a first proof of concept. It's built on top of the new global error
handling mechanism

Things to d

central logging mechanism

This introduces a logger mechanism and a new data/log directory. This is
a first proof of concept. It's built on top of the new global error
handling mechanism

Things to discuss:

* should we adopt PSR-3 somehow? if yes, how and should plugins be able
to drop-in other psr3 loggers?
* how to configure which facilities shall be logged?
* should we implement a log deletion feature?
* is the log format sensible?
* should we implement a log viewer admin plugin?
* should logging trigger events (it should maybe replace the
deprecation event)

show more ...

use $INPUT instead of $_SERVER

split out two form creation methods of ResendPwd

we can use prefillInput feature of InputElement class, no need to refer $INPUT in formResendPassword()

no need to convert Errors to Exceptions

we handle Throwables anyway

FatalException and proper plugin detection

Using our own Exception makes it easier to differentiate fatal errors
from others in the log

add shutdown handler to even manage fatal errors

We can't catch some errors and they are not passed to the error_handler
either. But we can at least react to them in a shutdown function to show
a fr

add shutdown handler to even manage fatal errors

We can't catch some errors and they are not passed to the error_handler
either. But we can at least react to them in a shutdown function to show
a friendly message to the user and write our log.

show more ...

reflow overlong line

better exception handling on plugin loading

Now all important places where plugins are loaded are guarded by a
try/except. We're catching Throwables here to be able to catch stuff
like syntax errors

better exception handling on plugin loading

Now all important places where plugins are loaded are guarded by a
try/except. We're catching Throwables here to be able to catch stuff
like syntax errors early on (otherwise they will only be caught by our
ErrorConverter much too late). This means that this change requires PHP
7.0 minimum!

show more ...

log stacktrace to error log

Ultimately the one responsible for fixing the problem will need this
anyway. Better log it right away for (hopefully) better bug reports

guess which plugin was the source of an exception

This looks at filenames and classes involved in the stacktrace to see if
a plugin is referenced.

We're only guessing plugins here, because looking

guess which plugin was the source of an exception

This looks at filenames and classes involved in the stacktrace to see if
a plugin is referenced.

We're only guessing plugins here, because looking for templates may
cause false positives where templates load plugins.

show more ...