Textpattern CMS

#133 2025-03-26 20:19:40

etc

Developer

Registered: 2010-11-11

Posts: 5,342

Website GitHub

Re: etc_search: when the default search is not enough

jakob wrote #339368:

I also discovered that etc_search_result_count does work if you explicitly specify a text attribute; the standard text string was reallocated to a new language string group in the core at some point and was no longer available to the plugin. I’ll make that a plugin textpack string and that should work again.

Good catch, showing_search_results string has somehow migrated to the admin side (why?)

However, it has to appear after etc_search_results. You can switch the order by first outputting the results to a txp:variable, then showing the result count heading, and outputting the variable. txp:items_count does however work above the etc_sarch_results tag.

You can also alter the processing order: <txp:etc_search_results[1] ... /> or <txp:etc_search_result_count[-1] ... />. As for <txp:items_count />, it makes use of the secondpass, postponing itself if no pagination data is available.

---

bloatware

#134 2025-03-26 21:12:33

Bloke

Developer

From: Leeds, UK

Registered: 2006-01-29

Posts: 11,677

Website GitHub

Re: etc_search: when the default search is not enough

etc wrote #339371:

showing_search_results string has somehow migrated to the admin side (why?)

Mistake. Probably me when I rejigged the strings. Sorry.

---

The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp