php7 syntax fix.
https://forum.dokuwiki.org/thread/15725
https://forum.dokuwiki.org/post/58606

php7 syntax fix.
https://forum.dokuwiki.org/thread/15725
https://forum.dokuwiki.org/post/58606

This should make their purpose more obvious.

This add some search assistance to simple, single-word search queries
which may be restricted to a single namespace.

Further improvements:
* better styling
* trigger events for other plugins
* set namespaces directly from fulltext search results
* some more config options

This also adds the default theme color for the DokuWiki template as the
green from the existing links.

The goal is to make the css replacement accessible in other contexts,
for example for the manifest.

typo

I'm not sure that setting the constants in template.php is the best
place. However if we set them in doku.php, we have to duplicate it in
lib/exe/mediamanager.php and lib/exe/detail.php, which is not ideal as
well.

This adds some simple defaults for the guaranteed placeholders. This
ensures plugins can safely use these placeholders even when a template
did not implement them.

This doesn't really do much except wrapping the functions into a
namespaced class. Autoloading takes care of loading the file.
It's now possible to call lib/exe/ajax.php multiple times in a test
request.

added test coverage

While DokuWiki suppresses PHP Notices they are still a code smell and
should be fixed. This fixes some PHP Notices that occurred.

Some of these fixes could be refactored into nicer code once we move to
PHP 7 and get access to the `??` operator.

No need to check those seperately. The correct order should be ensured
already.

This also removes duplicated code from ajax.php

This is important because the $cache->cache would have been set already and have no impact on the delivered result. Meaning: two different requests could have resulted in the same result.

Remove the flavour feature. It was some kind of a hassle. If you really want to filter out styles, you have to write a plugin either way and implement the tpl metaheaders event as well and handle everything your self.

The CSS modification is more like the JS_SCRIPT_LIST now. It adds some overhead, but not too much. It still gives great flexibility over the CSS.

Changed the cache initialisation: it does not use the list of files with an md5 (due to redundancy and time consumption) but the flavour and the type (previously removed).

Use the flavour system to create individual css files. Only the default flavour (style / style.ini) will have the default styles for interwiki and filetypes. There are two new events:

 1. CSS_STYLES_INCLUDED to modify the list of stylesheet files for a certain mediatype or prevent the mediatype or styles within it. This event is fired for the interwiki and filetypes too, to prevent that they are included
    * The Data that is being sent to the event contains: list of files or the keyword DW_DEFAULT for the interwiki / filetypes; the mediatype, the flavour, if the data should be encapsulated by a default @media and the encapsualation prefix (e.g. @media screen)
 2. CSS_CACHE_USE to prevent the use of a cached version of the CSS, just like the JS event that already exists.

Add flavours to template ini files. The template will now be checked for multiple ini files and inserts them as a custom flavours. The css.php can detect these flavours and reads the stylesheet + replacements from there. If the flavour is not the default one (style.ini), replacements are loaded from the default flavour first to ensure that the colours are available. Flavours can define their own set of replacements.

Remove type and caching mechanism. The cache will be checked later and the type will be replaced by an md5 hash of the list of style files.