D/B warning error after update to J4 Topic is solved

[sclg]

I've updated a site to J4.
No errors flagged during the update. All extensions, templates, etc updated to J4 compliant versions.
Cleared out any 'leftover' tables and folders from old extensions, etc.
Everything in the front end works fine.
The only problem is that Maintenance:Database shows 2 warning errors...

Code: Select all

Warning: Attempt to read property "schemapath" on null in D:\wwwroot\pensions\administrator\components\com_installer\src\Model\DatabaseModel.php on line 180

and

Code: Select all

Warning: Trying to access array offset on value of type null in D:\wwwroot\pensions\administrator\components\com_installer\src\Model\DatabaseModel.php on line 180

Tried turning on the various debug options but I don't get any more information.
Any thoughts on what might cause this please?
I can post the FPA output if required.

Thanks

[sclg]

I know it is no help but I have exactly the same problem and have had no responses to my requests for ideas either.
I also tried removing all extensions and it didn't cure it.

[ceford]

Reading the code, it seems the installer is looking for the sql/updates folder of each extension and runs into trouble if a folder is not found and a schema is not found in the component installation data.

You could try planting this code in line 178 of administrator/components/com_installer/src/Model/DatabaseModel.php

file_put_contents(JPATH_ADMINISTRATOR . '/logs/log_test.log', $folderTmp . "\n", FILE_APPEND);

Then reload the Maintenance: Database page and immediately open administrator/logs/log_test.log with a text editor. You should see the path to the missing folder and that should tell us which extension is causing the problem.

Do not forget to remove the planted line immediately after the test!

[sclg]

Reading the code, it seems the installer is looking for the sql/updates folder of each extension and runs into trouble if a folder is not found and a schema is not found in the component installation data.

You could try planting this code in line 178 of administrator/components/com_installer/src/Model/DatabaseModel.php

file_put_contents(JPATH_ADMINISTRATOR . '/logs/log_test.log', $folderTmp . "\n", FILE_APPEND);

Then reload the Maintenance: Database page and immediately open administrator/logs/log_test.log with a text editor. You should see the path to the missing folder and that should tell us which extension is causing the problem.

Do not forget to remove the planted line immediately after the test!

You are a genius!
Now I know it's the Cookie Policy Notification extension and can follow up on that and try uninstalling/reinstalling.
Many thanks