…171049

Translation update (zh-tw)

…447225

Translation update (uk)

Bump $updateVersion to 56

Output more version data on the admin screen

🤖 Automatic code style fixes

Log in local time instead of utc

…776471

Translation update (pt)

…770377

Translation update (ko)

Remove obsolete translation

The Woltlab forum software uses bcrypt passwords, but prefixes them with
"Bcrypt:". This adds support for this in our PassHash class.

Moving JWT token store away from cache directory,
to have long-lived authentication files properly stored.

Using sha256 on the files instead of md5, to help mitigate
potential hash collision as filenames are based on username.

Move JWT token into metadir #4239

Run autoFix only if repository owner is dokuwiki

Run autoFix only in dokuwiki repo

…252389

Translation update (tr)

This prevents metadata export in general and also ensures the the
temporary $doc property in the metadata renderer is cleared in
document_end

Use date in install.php

Support Woltlab password hashes

fixes #4308

The B flag reenables passing spaces and other special chars in URLs to
be picked up (and cleaned) by DokuWiki's ID processing.

The flag has been available in non-broken form since Apache 2.2.9 and
should be safe to use.

See https://stackoverflow.com/q/3460643

If opcache is enabled, but access to it's API is restricted a warning is
shown when we call opcache_reset(). Since we don't know if it's
restricted, we have to supress the warning

Add experimental tree builder classes

use B flag for Apache rewrite rules. fixes #4238

This addresses #4400. By checking the context visibility after the
assembly, the context is properly checked for plugin items.

I am not sure why moving the context visibility check to a later stage
suddenly surfaced the issue of $INFO not being set in the
general_html_test. I would have expected the same issue before the
changes of 33792c0

In any case it makes not much sense to do the permission checks there
anyway. Doing it in the constructor makes more sense since this is not a
context sensitive check.

…4637141

Translation update (pt)

If the `at` url parameter contains a value that is neither a date nor a timestamp integer then prevent the date() function to fail due to an illegal parameter type.

For example given `&at=xxx` this would happen before this patch.

Firefox (128 esr on Linux) displayed a solid black border around all buttons inside the popup which makes it impossible to see which button was pressed. This change makes the outset/inset look work as it probably was intended.

Menu: check context visibility after assembling items

Better deal with at url parameters that have weird values

fix button border css

verified via  ?do=export_htmlbody

…5211223

Translation update (ru)

…7106614

Translation update (es)

…7191205

Translation update (es)