The actual draft text got lost when we changed to showing the diff
instead of the full draft.

Specifically, this pull request checks if the current query is already a
valid pageid and then return that as suggested pageid.

Also, tests are added for this method.

Fixes #2355

PS: We may want to somehow better educate/nudge users to use the better
way of creating pages by creating links on existing pages.

and actually use it in the edit form.

This bug was introduced in #2251
c4a386f1

Fixes #2325

Also, for consistency this initializes also $num with 0, while ensuring
that the first FT_SNIPPET_NUMBER results with a $cnt>0 have a snippet.

Punctuation is more natural, makes sense with CSS switched off
and makes screenreaders add a little pause.

In #2286 the 2nd level heading in the intro was removed, so the h3
should be promoted to h2.

This implements some of the changes discussed in #2314:

1. last mod and number of hits are on the same line and always shown
2. There is a class around the last mod string so it can be
hidden/replaced by an icon
3. All items in the resultBody returned by the event are wrapped in
`<dd>` tags to ensure validity. They get their array key as class
4. There is still a wrapper div around each result for styling purposes

Recent changes to the search results page added various divs
to the pre-existing description list, which is invalid.
This fixes that by a) removing a couple of unnecessary elements
and b) interpret the 'last modified' line as another 'dd'.

The advanced search options list links with an invalid empty target
attribute. This fixes that by skipping empty parameters.

The search buttons from the search form on the top of the page
as well as the search page both produce invalid HTML
due to the name attribute being empty.
As the name is required for each of the PHP functions
producing the buttons and is passed as an empty string,
this makes sure that parameters with empty strings get skipped.

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.