This makes it a little easier to splice new elements into position

This function is now deprecated.

Tests even surfaced some smaller bugs :-)

Othewise weird side effects may happen when a parent constructor
overwrites them again.

Even for our own namespace, file existance should be checked before
attempting to load it. Otherwise class_exist() check will throw errors.

Various plugins access the form members directly currently.

getLink() now no longer escapes ampersands - this is task of the code
producing the HTML. When using asHtmlLink(), buildAttributes() will take
care of the escaping for you.

Adjusted pattern for matching media links to properly handle a single '}' in the link text. Fixes #1587.

This basically reimplements tpl_action_dropdown but makes use of the
other menus (by setting the context to mobile) and thus still triggers
the appropriate events. This makes #1598 obsolete.

tpl_action_dropdown (and the other tpl_action* methods) still need to be
replaced to make use of the new Menu system.

this adds an option to print the menu without icons (as we do in the
dokuwiki template) but icons were added nontheless

also adjusts styles and adds images

This is an attempt to:

* get rid of the super long, complex functions in in/template.php
* make it easy for plugin authors to add their own items to any
  of our menus, regardless of the used template
* continue the progress to make use of SVG in the menues

This takes a similar approach as my actionrefactor branch. Originially
I thought both refactorings could be done in one, merging the
functionality of DokuWiki actions and the menu items. However I couldn't
make it work. So instead we have two separate but similar things.
Maybe they can converge later on.

If an entry in the loop at `_tpl_metaheaders_action` has no content, skip this entry.

There are still some left in the DifferenceEngine code

This should fix some tests on PHP 7.1. The work is far from done, we
still have a lot of variables without proper accessibility defined.

This change breaks compatibility with php 5.3.7, but a standing
requirement for at least php 5.6 is declared in composer.json.

If the php documentation is to be believed, this change increases
security against pass-the-hash type attacks. (I do not have the knowledge
to assess the security differences between $2a$ and $2y$).

As a Sidenote: htpasswd shipped with apache2 2.4.10 (and probably,
other versions), when used with the -B (=bcrypt) option, produces hashes
marked with $2y$.

Nonewithstanding the actual support or non-support of $2a$ by the
apache2 'AuthUserFile' directive, the apache 2.4 documentation only
asserts support for the $2y$ bcrypt variant.
Therefore, this commit would make it possible for dokuwiki and apache2
basic authentication to share the same password file, in the case when
bcrypt is used.

I supplemented the existing comments on the methods in which there was not enough information to the standard phpDoc.

I supplemented the existing comments on the methods in which there was not enough information to the standard phpDoc.

I supplemented the existing comments on the methods in which there was not enough information to the standard phpDoc.

I supplemented the existing comments on the methods in which there was not enough information to the standard phpDoc.