Before this change, HTML and some JS code (as far as it was not escaped
by json_encode) could be injected into the output as the closing pattern
that is checked by the regex is not escaped in JSON (see test case).

The displayed message now shows the target that was passed, which should
help identifying the troubling plugin.

Instead of failing, we fix the data ourselves - this code will be
removed in the future.

This fixes a bug that would occur if the DokuHTTPClient receives a 204
response, e.g. as a result for a request to delete something. It would
still try to read the body, which fails, thus producing a timeout and
finally throwing an exception.

This fix instructs the HTTPClient to not read the (not existing) body if
it receives a 204.

Quotes are now optional, the options are spearated by space

This was unintentionally removed in
4eab6f7c

It also should now be clearer what the code does.

This fixes #2305

As discussed in #1933

shorter names are more in line with what we already use, makes less
layout problems in the documentation and is easier to type when telling
people about it.

This fixes broken nested section edit buttons which were causing
invalid HTML code. The pattern has to be 'not greedy'. Fixes #2304.

This should give us some backwards compatibility for changing files in
dokuwiki template from .css to .less

This way template authors get a warning to adjust their template, it
won't break right away.

This should prevent breaking search pages in other templates due to
pull request #2286 .

This is a more consistent place relative to pageinfo()

json_encode is available natively since PHP 5.2

This should make their purpose more obvious.

They are now named min and max respectively, which is hopefully less
cryptic.

This is useful for anonymously useable forms, like the search.

Pressing enter in the small quick-search-box while it was empty resulted
in a search for the current pageid.

Since we no longer change the page during a search, using the "show"
menu item to return to the current page makes more sense.

This way they can be cleanly influenced by the plugins instead of having
to modify global state.

As suggested by @splitbrain SearchState now behaves simliar to the PSR-7
message interfaces.

Implements the functionality requested in #1124

This removes a lot of reudundant CSS classes in favor of cascading
selectors. Styling isn't done, yet this is just a first step.

Still to do:

* aria labels
* styling the toggle mechanism
* RTL styling
* making sure everything displays correct when no JS is available
* translations may be missing
* refactoring the rest of search.less to make use of LESS features

This also renames the event for the search form on the search page.

The scheme for naming events that provide the new Form-class as $data is
FORM_<formname>_OUTPUT