Meanwhile I was able to identify the critical SQL query which causes the reported issue, and I have created a pull request (PR) with a fix: https://github.com/joomla/joomla-cms/pull/42576 .
As usual it needs 2 human tests, and it has already one, so it just needs one more test, and if we get it ready until Monday it will be included in the upcoming 4.4.2 and 5.0.2 releases. So if you want to help: Test it and report your test result in the issue tracker https://issues.joomla.org/tracker/joomla-cms/42576 . Just follow the testing instructions in that PR.
The PR will fix the issue for the Joomla core for the Update view of the Joomla Update component when an update is available and the pre-update check is shown, and for the Extensions Manager when filtering for core or non-core extensions, so it will not need anymore the workaround described in previous posts.
As usual it needs 2 human tests, and it has already one, so it just needs one more test, and if we get it ready until Monday it will be included in the upcoming 4.4.2 and 5.0.2 releases. So if you want to help: Test it and report your test result in the issue tracker https://issues.joomla.org/tracker/joomla-cms/42576 . Just follow the testing instructions in that PR.
The PR will fix the issue for the Joomla core for the Update view of the Joomla Update component when an update is available and the pre-update check is shown, and for the Extensions Manager when filtering for core or non-core extensions, so it will not need anymore the workaround described in previous posts.
Statistics: Posted by Richard67 — Sat Dec 30, 2023 10:14 am