If you are using the TS property forwardSearchWordsInResultLink in indexed_search, currently the links to result pages will always have an added no_cache=1.
This is due to the fact, that normally the search word forwarding is marked on the result page by lib.parseFunc.sword (lib.parseFunc_RTE.sword respectively) and those parseFunc settings may have no effect on cached pages.
There might be circumstances, where you want to forward the search word but not linkníng with no_cache=1 (of course) - so this report suggests to enable the user of indexed_search to turn off this default behaviour by a new TS property:
plugin.tx_indexedsearch.forwardSearchWordsInResultLink.no_cache = 0 (default should be 1 to keep existing setups working)
[FEATURE] no_cache for forwardSearchWordsInResultLink configurable
Adding the TS property
which allows disabling the no_cache=1 parameter for result page links
when plugin.tx_indexedsearch.forwardSearchWordsInResultLink is enabled.
Default is 1 so that there isn't change of behaviour in existing setups.
Reviewed-by: Tymoteusz Motylewski <firstname.lastname@example.org>
Tested-by: Tymoteusz Motylewski <email@example.com>
Reviewed-by: Benni Mack <firstname.lastname@example.org>
Tested-by: Benni Mack <email@example.com>