After Upgrade Wizard: Add the default Extension Manager database tables - Reports Update Incomplete
Tested on clean installed 9.5.0, 9.5.1 and upgraded 8.7 to 9.5.1, always the same problem:
After I run the Upgrade Wizard "Add the default Extension Manager database tables" I get the warning on start screen:
One or more problems were detected with your TYPO3 installation. Please check the status report for more information.
And in the reports:
This installation is not configured for the TYPO3 version it is running. If you did so intentionally, this message can be safely ignored. If you are unsure, visit the Update Wizard section of the Install Tool to see how TYPO3 would change.
Upgrade Wizard says: 100%
Analyze Database Structure says: Database schema is up to date. Good job!
Second issue or hint:
After that I have installed the news extension, then the Upgrade Wizard says 50% and wants me to execute the wizard "Add the default Extension Manager database tables" again.
After that I go to the Database Analyzer. It brings several database changes:
ALTER TABLE `tx_news_domain_model_news` CHANGE `uid` `uid` INT AUTO_INCREMENT NOT NULL
Current value: uid INT UNSIGNED AUTO_INCREMENT NOT NULL
ALTER TABLE `tx_news_domain_model_news` CHANGE `tstamp` `tstamp` INT DEFAULT 0 NOT NULL
Current value: tstamp INT UNSIGNED DEFAULT 0 NOT NULL
ALTER TABLE `tx_news_domain_model_news` CHANGE `crdate` `crdate` INT DEFAULT 0 NOT NULL
Current value: crdate INT UNSIGNED DEFAULT 0 NOT NULL
I have selected all and executed, then it says: Database schema is up to date. Good job!
I go back to the Upgrade Wizard, it says 50% again as above. It's like a loop.
#8 Updated by Christoph Hendreich over 1 year ago
- PHP Version changed from 7.2 to 7.3
Got the same problem. PHP 7.2, TYPO3 9.5.7
Looking for a problem with tx_new, as soon as the extension is uninstalled and database compare the behavior does not occur anymore.
After re-installation the problem is present again.
#12 Updated by Markus Klein almost 1 year ago
I pushed a patch, which could potentially fix this issue as well: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62154
Kindly asking for tests.