Hi,

great idea to enhance the plugin. I think it will be very helpful for wikis with a distinctive structure.

One thing I found in my first tests: Obove the search results a code line is displayed.
For example if I search for 'Material' in the root namespace, the line is:
'string(5) "no ns" string(8) "Material" '
If I search in a specific namespace the code line for example is:
'regexpint(0) array(0) { } string(4) "a ns" string(69) "Material @technik:verwaltung_mit_sap:dokumentverwaltung:cdesk:modelle" regexpint(0) array(0) { } string(4) "a ns" string(69) "Material @technik:verwaltung_mit_sap:dokumentverwaltung:cdesk:modelle" '

Regards
Juergen

How can i exclude a namespace from search?

Like: ns:search -ns:nosearch

Hi :)

I am currently running DokuWiki Release 2018-04-22c "Greebo" from a Synology NAS. I have been using this setup for several years and everything usually works smoothly.

Recently I updated several plugins via the Extension Manager in the Admin Admin panel, including this plugin (Search Form Plugin).

Since this update, all pages that include {searchform} are no longer displayed (black screen) and tools on the right-hand toolbar are no longer available (buttons not displayed), e.g. edit page, previous version, manage subscriptions, ...

Disabling the plugin makes the pages to be displayed properly again (although obviously {searchform} is displayed rather than the search field). Re-installing the plugin doesn't fix anything (black screen).

I don't know what I should do. I don't know what other info could be relevant in this case.
Synology NAs runs the following packages: PHP7.2, PHP7.0, PHP5.6. I don't know if this is relevant.

Thank you very much in advance for your help, guidance and advice.
Best,
-a-

Can it be made so that you can specify the namespace to search relative to the current page like described in the namespaces help page:

Links relative to the current namespace may also begin with either “.” or “.:” (“..” or “..:” for parent namespace).

Eg1
{searchform ns=.: } or {searchform ns=. }
will search in the current name space
Eg2
{searchform ns=.:policies }
will search in the polices sub-namespace of wherever the page is

That way I can use the variables and include plugins and have a standard "search" section defined centrally that I can refer to from other pages.

======search======
===== Searching in the @NS@=====
You can use the search box at the top of the page to carry out a search of all documents in the wiki or the form below to search just the @NS@section : 

{searchform ns=.:}

More search syntax options can be found [[https://www.dokuwiki.org/search|in the documentation]].

that will allow me to include in any page:

{{section>:common_elements#search&noshowheader}}

or have as part of a page template.

I gave it a go to see if it would work but it ignored the . and .: and just searched the whole wiki.

I tried using @. or @.: in the standard page search at the top of the default template and it ignored them.

I had a quick look at the code for the plugin but wasn't able to see how to get the ns of the current page if the ns string passed as a parameter in the markup was either . or .:

After update to the new version the following is on top of the page:

Array ( [namespace] => namespace1:namespace2 [excludens] => )

Pagecode: {searchform ns=namespace1:namespace2}

downgrade to the old version, error is gone. can you please check.

Seems like some method signatures are missing. Our logs are full of:

PHP Warning:  Declaration of syntax_plugin_searchform::render($format, &$renderer, $data) should be compatible with DokuWiki_Syntax_Plugin::render($format, Doku_Renderer $renderer, $data) in /var/www/html/ttp/lib/plugins/searchform/syntax.php on line 0, referer: https://www.google.de/

and similar messages concerning syntax_plugin_searchform::render and syntax_plugin_searchform::handle

Can the plugin be adapted for the latest version "Hogfather" of DokuWiki?
Basically I think the plugin is very good and would be glad if it would be maintained further.

literally tittle ..
i can not found any options