Project

General

Profile

Actions

Bug #101289

closed

Error on excuting upgradewizard "sysLogChannel" in TYPO3 12

Added by Karsten Nowak (undkonsorten) over 1 year ago. Updated 5 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2023-07-07
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
12
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

I'm using a database dump from a TYPO3 9.5 instance and try to execute the update Wizard "sysLogChannel". Database schema is up to date.

On excuting the wizard (cli and backend) an error is shown.

Uncaught TYPO3 Exception #1: assert(is_int($param))
thrown in file /app/vendor/doctrine/dbal/src/Driver/Mysqli/Statement.php
in line 105

Even if I truncate or delete the sys_log table (created new afterwards) the error is shown.

After executing the wizard, he is not longer visible in the list of u pgrade:list

Local docker system with php 8.2, MariaDB-1:10.3.29, TYPO3 12.4.2

Actions #1

Updated by Georg Ringer over 1 year ago

  • Status changed from New to Needs Feedback

without knowing more details it is hard to find the problem. however a direct upgrade from 9LTS is not supported, please run first all upgrade wizards in a TYPO3 10 LTS and then you can switch to a v12

Actions #2

Updated by Karsten Nowak (undkonsorten) over 1 year ago

I'm using the core_upgrader2 extension to use the other wizards. The sysLogChannel wizard come from core. Therefore I thought that's not a problem of the extension. But the order of execution is a godd hint. I will check this.

Actions #3

Updated by Karsten Nowak (undkonsorten) over 1 year ago

  • % Done changed from 0 to 50

I tested the wizard with the same database in TYPO3 11 instance. No errors.

It seems to me that the sysLogChannel wizard only properly works in TYPO3 11, not in TYPO3 12. However, it's working for me in TYPO3 11. That's ok for me.

But in TYPO3 12 maybe the wizard has a problem with the doctrine/dbal package?
I'm using doctrine/dbal 3.6.4

To reproduce the error it should be enough to have an empty sys_log table with schema of TYPO3 9.5.

Actions #4

Updated by Gerrit Code Review over 1 year ago

  • Status changed from Needs Feedback to Under Review

Patch set 1 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/80169

Actions #5

Updated by Gerrit Code Review over 1 year ago

Patch set 2 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/80169

Actions #6

Updated by Elias Häußler over 1 year ago

I can confirm this on TYPO3 12.4.4 and just pushed a patch that solves the issue for me.

Actions #7

Updated by Anonymous over 1 year ago

  • Status changed from Under Review to Resolved
  • % Done changed from 50 to 100
Actions #8

Updated by Benni Mack 5 months ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF