-
-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Site exception in indexing task since update TYPO3 11.5.38 to 11.5.40 #4191
Comments
Downgrading to TYPO3 11.5.38 didn’t solve the problem. I don’t know why. |
I already recreated the task but withoult luck, issue still exists |
@klodeckl , @seirerman Please provide more infos about your setup:
|
It is a multisite system, yes. Running the scheduler task only throws the same error message: Upgrade wizards are executed und database schema is up to date. |
On our TYPO3 11.5.39 projects we do no have any trouble. |
I didn't encounter any problems starting the Scheduler task in our solr-ddev-site environment with TYPO3 11.5.40. But I was able to provoke this error, it occurs if
Perhaps there is an issue with the TypoScript or the site configuration. |
Site configuration is set as usual, and solr TS is included. The frontend wouldn't work without it. Any specific values I should check? |
I had the same error, but the message was misleading. In my case, the following condition in the Typoscript was the problem:
I had to extend it:
You can also start the Debugger and set a breakpoint in All infos based on TYPO3 12.4.21. |
@seirerman No specific setting unfortunately I only did very basic tests and removed the TS includes completely. IMHO the hint from @dschlobohm regarding the misleading error message is a good point, a detailed look at the exception could help to identify the error. |
I don't have a condition containing "request.getNormalisedParams" anywhere in my code. This is from my log:
|
We're testing the upgrade to TYPO3 12 at the moment (with the plan to update all of our websites by the end of the month), and fortunately ext:solr 12.0.5 is not affected. Indexing works fine with TYPO3 12. |
I’m currently working on the update to TYPO3 12. I will test if the issue is also solved for me after the update and report it here. |
I can confirm this. After an update from TYPO3 11 -> 12 (+ solr 11 -> 12), I saw the error message that the OP posted (Argument must be Site, null given). In the scheduler, when adding or editing an IndexQueueWorker-task, the site select dropdown was empty. Changing ALL occurences of in our own sitepackage typoscript to the error message vanished, and the site selector drop down contained all configured sites. Attention: dschlobohms original post/code has a typo (getNormalisedParams, with an "s"). It must be getNormalizedParams (with a "z"). |
I've updated my post, thanks for the hint! |
Updatet to TYPO3 12 solved this problem for me too. |
We had a similar issue in combination with werkraummedia/abtest. tl;dr: It was a Hook that modified the TypoScriptFrontendController. We disabled it in CLI context. |
Wow, I wasted a day until I found this issue. In case it helps someone, in my case it was a TypoScriptConditionProvider registered via Configuration/ExpressionLanguage.php instead via Services.yaml after upgrading from 11.5 to 12.4. I wrote some custom indexers and these just could not get any solr site configuration anymore... |
I updated TYPO3 from 11.5.38 to 11.5.40. Now I get the following error when executing the indexing scheduler task:
Manually starting the task in the backend scheduler module works fine.
solr 11.5.6
PHP 8.2
The text was updated successfully, but these errors were encountered: