media: Fix media_resize_image cache check

The check was backwards, and it also caused a failure when there is no
cache file (mtime=0) because the function would still return the path to
the nonexist

media: Fix media_resize_image cache check

The check was backwards, and it also caused a failure when there is no
cache file (mtime=0) because the function would still return the path to
the nonexistent cache file.

show more ...

consistent html_buildlist() usage

see usage of html_buildlist in plugin acl (admin and action component)

re-declare deprecated functions for backward compatibility

`dbg_deprecated()` is called in `html_diff_head()`, `html_diff_navigation()`, `html_diff_navigationlink()`, and following functions:

* `h

re-declare deprecated functions for backward compatibility

`dbg_deprecated()` is called in `html_diff_head()`, `html_diff_navigation()`, `html_diff_navigationlink()`, and following functions:

* `html_denied()` is not used any plugins, but added fallback just in case.
* `html_locked()` is used by one third-party plugin (AjaxEdit), fallback should be added.
* `html_insert_softbreaks()` is used by one third-party plugin (TOS, terms of service), fallback should be added.

show more ...

translation update

add dbg_deprecated() calls

use Slika for image resizing and cropping

This replaces our own resize/crop function by the Slika library.

This is not yet ideal, as there is quite a bit duplicated code between
media_resize and me

use Slika for image resizing and cropping

This replaces our own resize/crop function by the Slika library.

This is not yet ideal, as there is quite a bit duplicated code between
media_resize and media_crop now. Ideally these two should be replaced by
a single method handling both. I'm just not sure where to best put it
yet.

Using Slika introduces two new features:

* auto rotation based on EXIF #3059
* support for webp #3238

show more ...

translation update

change event naming scheme

FORM_*_OUTPUT scheme had been introduced since Apriil 2018, see #2286

fix Scrutinizer annotations

fix Scrutinizer annotations

fix missing or unnecessary use Event statements

tigger HTMLFORM_*_OUTPUT events

trigger events in Form::toHTML() instead of using Event::createAndTrigger()

Form::toHTML() can trigger event

New event naming scheme HTMLFORM_*_OUTPUT should be tiggered to prevent break of old third-party plugins using old events HTML_*FORM_OUTPUT.

translation update

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().

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.

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 ...