#106130Indexed search plugin show error message "No TypoScript found" even if you added TypoScript
Description
When TypoScript is not loaded or the site set not included, any action forwards to the
noTypoScriptAction. This action does no further checks but just displayes the error message.
So if you include the site set, delete all caches and reload the page the same error is still
being displayed.
I would suggest we use a forward instead of a redirect or add a check in the method if TypoScript
is indeed still not being included.
Reviews 2
History 37
-
Gerrit Code Review pushed patch set 1 for main to change 88138 status
NewUnder Review <span data-processor="relativetime" data-value="2025-02-10T15:26:53+00:00" > 02/10/25, 15:26 </span> -
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-02-10T15:28:15+00:00" > 02/10/25, 15:28 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 88152 <span data-processor="relativetime" data-value="2025-02-10T20:24:54+00:00" > 02/10/25, 20:24 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 88138 <span data-processor="relativetime" data-value="2025-02-10T20:27:13+00:00" > 02/10/25, 20:27 </span>
-
Gerrit Code Review pushed patch set 2 for 13.4 to change 88152 <span data-processor="relativetime" data-value="2025-02-10T20:27:20+00:00" > 02/10/25, 20:27 </span>
-
Garvin Hicking commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-02-10T21:00:09+00:00" > 02/10/25, 21:00 </span>Applied in changeset commit:d62ddacb0ed8bfd6692d1882e217bad5b98b4df9.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-12-02T14:27:37+00:00" > 12/02/25, 14:27 </span>
Good suggestion; I’ve opted for the forward approach. My reasoning is that a check for fulfilled valid typoscript in the
noTypoScriptAactionwill not (easily) be able to go back to the original request’s target, and would then still be a bad developer experience.