improve search results

colak · 2022-05-31 13:32:07

One of the problems with the search results is the way it omits spaces.
The name Chang for example v the word change are both returned even if a space is added after the name.
This is something that has already been solved in smd_where_used where Chang only returns the name and Chang returns occurrences of both the name and the word.

Bloke · 2022-05-31 14:45:35

Yes but some people might actually want that wildcard search behaviour. My plugin uses binary search if I remember correctly. Having an option in the search tag to switch on binary might be handy if we don’t have that already.

etc · 2022-05-31 15:17:42

You can try m="natural" attribute. Somewhat related?

See the difference between www.neme.org/?m=all&q=peint and www.neme.org/?m=natural&q=peint

Pat64 · 2022-06-01 12:24:50

etc wrote #333474:

You can try m="natural" attribute. Somewhat related?

I’m so curious (because the results are the kind I’m looking for): where is this m="all" attribute for (in which mysterious tag)? 🤔

etc · 2022-06-01 19:35:14

It’s actually called match (natural is undocumented though), but all it does is append m=matchtype to the search URL.

Pat64 · 2022-06-02 02:18:45

I tried to set the match attribute on natural instead of any for the <txp:search_input /> tag.
The request URL didn’t inject any m parameter (Textpattern 4.8.8.)…

phiw13 · 2022-06-02 06:35:11

How do I add this attribute if I use a form (customised template for the search form)?

Take for example the default templates / theme on the demo site.

the body_header.txp form inserts the <txp:search_input /> tag and it automatically uses the search_input.txp form. However if I add the match attribute – it ignores
that form (and the HTML form construct it contains) for the front-end output and uses a very basic HTML form. But

<txp:search_input match="any" form="search_input" />

ignores the match attribute (that is, the search url is domain.test/?q=crazy+string). ??

The one way I now found is adding this as a hidden input into my form construct – inside search_input.txp form:

<input name="m" type="hidden" value="any">

that does result in the expected domain.test/?m=any&q=crazy+string

Pat64 · 2022-06-02 07:26:05

You’re right, Philippe.
Thank you so much: your solution is perfect and works well. 👌

phiw13 · 2022-06-02 07:46:52

Pat64 wrote #333505:

You’re right, Philippe.
Thank you so much: your solution is perfect and works well. 👌

Thanks :)

BTW can someone with admin spellchecking powers correct the thread title

etc · 2022-06-02 10:40:01

phiw13 wrote #333504:

<txp:search_input match="any" form="search_input" />...

ignores the match attribute (that is, the search url is domain.test/?q=crazy+string). ??

Indeed, it only honours match attribute when form="" is set. Otherwise the care of m input inside the form is left with the user, to avoid duplicates. Is it a bug? Dunno..

phiw13 · 2022-06-02 11:27:41

Bug maybe not, but it wasn’t at all clear from the documentation. If my attempt above is the way to go, that is perfectly fine with me. Thanks for the feedback.

gaekwad · 2022-06-02 12:11:13

phiw13 wrote #333506:

BTW can someone with admin spellchecking powers correct the thread title

Done.

Textpattern CMS

Textpattern CMS support forum

#1 2022-05-31 13:32:07