Closed phil64 closed 3 months ago
Actually, the problem is broader, because the entire configuration of the searchplugin of my page is ignored by the search request (the starting point, the filters...). The only solution I currently have is to deactivate the "general" plugin injected in typoscript on the page.
I can see the point, but I think that's not so easy to resolve because of the the DB class being a singleton class as you already mentioned.
Would it be a workaround for you to add the search form in the header not via a plugin but via plain HTML as described in https://docs.typo3.org/p/tpwd/ke_search/main/en-us/Templating/Searchbox.html?
I understand that this is not easy to resolve. I will try with the HTML solution. For now, I just disabled the TS plugin injected on my specific page, it's ok for my use
My configuration:
My results list is configured to get the starting point of this search plugin, via loadFlexformsFromOtherCE. But in the Db singleton class, the setPluginbase method is initialized with the first search plugin on the page, and therefore with the wrong starting point in the getWhere() method thereafter.