Correction: PHP 8.0.11

Does the page with the button show a table with rows, one for the CMS core and the possibly more rows for 3rd party extensions? Each of these rows should have a badge showing if there are problems found or not, and when a badge shows that there are problems, details are shown in a tool tip when hovering the badge.

To fix probles it first needs to select the corresponding row(s) before using the “Fix” button. Each row has a check box at the left side for selecting it, like all the other list view in backend have.

Please report back. if possible with screenshots, how that page looks for you and which problems were found and if the “Fix” button works for you when having selected a row.

if the page does not show any rows, please report back which 3rd party extensions you have installed, because very likely it would be a syntax error in an SQL update script if such an extension which causes the database checker break.

Thanks in advance.

It’s a new feature in Joomla 4 that the database checker checks not only the CMS core but also 3rd party extensions if they have update SQL scripts.

I attached a screenshot of what I've seen. There is no fix button.

Looks like cloudaccess.net ( the joomla.com hoster ) is working on
something, because the site is extremely slow I get kicked out after
about only one minute of being logged in.

On Wed, 27 Oct 2021 at 20:53, Richard Fath @.***> wrote:

Does the page with the button show a table with rows, one for the CMS core
and the possibly more rows for 3rd party extensions? Each of these rows
should have a badge showing if there are problems found or not, and when a
badge shows that there are problems, details are shown in a tool tip when
hovering the badge.

To fix probles it first needs to select the corresponding row(s) before
using the “Fix” button. Each row has a check box at the left side for
selecting it, like all the other list view in backend have.

Please report back. if possible with screenshots, how that page looks for
you and which problems were found and if the “Fix” button works for you
when having selected a row.

if the page does not show any rows, please report back which 3rd party
extensions you have installed, because very likely it would be a syntax
error in an SWL update script if such an extension which causes the
database checker break.

Thanks in advance.
It’s a new feature in Joomla 4 that the database checker checks not only
the CMS core but also 3rd party extensions if they have update SQL scripts.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#35915 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD6U3NZIXPTACP33GDQORGDUJBKCPANCNFSM5G2TL66A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@XenoEgger I don't see any screenshot, but as I understand it would not really show much, so that's ok. Let us know here if there is something new.

Well, I attached the screenshot to the e-mail. Guess that didn't work. So I had to log in to GitHub again.. :((

The only things I did to the automatic, fresh installation @ joomla.com was: Login as admin. I didn't do anything else!
Then I tried to update because Joomla told me that 4.0.4 is available.

This is what I ( sometimes, because sometimes it says 4.0.3 is up to date..... ) see when I click to update Joomla

:

@XenoEgger Could you go to the “System” panel and there to section “Manage” and there select “Extensions” and then in the list view of extensions sort by ID in descending order so you see those with the highest ID at the top and then make a screenshot and then post it here? Thanks in advance.

I hope the first page is enough.

Hmm, I see no additional extensions ... I have no idea.

@XenoEgger Do you have access to your database e.g. with phpMyAdmin?

If so: Could you make an export of the database into an SQL file? It is sufficient if you export only the structure but not the content (which might be confidental so you don't want me to know).

You can do that by selecting the database in phpMyAdmin, then chose "Export" in the top tab bar, then change "Export method" from "Quick" to "Custom" and then in the table shown below the "Formal" selection, which should be "SQL", make sure that the "Structure" check box of each table is checked and the "Data" check box is not checked for all tables. You can select or deselect all by using the check box in the table header.

Then zip the exported SQL file and send it to me, using the contact form of my home page .

Update: Ah, I see you can't send attachments with my contact form. So just send email to admin<at>richard-fath.de (replacing the <at>by an at of course ;-) )

Maybe I get an idea what could be the database problem when I have that, so it could really be a help.

Thanks in advance.

@XenoEgger Please apply the changes from pull request #35951 and check if you now can see anything on the "System - Maintenance - Database". If yes, hover over the badge which shows the problem as described in that PR in the testing instructions so you can see the problem details and make a screenshot so we can find out what your problem is.

And mark the test result for that PR as successful in the issue tracker if it works as described so you can see the error details. For doing this you go to the issue tracker here https://issues.joomla.org/tracker/joomla-cms/35951 , use the "Test this" button, select the right test result and submitt.

Thanks in avdance.

Closing as having a pull request. Please test #35951 . Thanks in advance.

I have exactly the same problem on Joomla 4.0.6 running on joomla.com (CCP).

Wanted to update to Joomla ‎4.1.0-rc2, but:

I am running this website from beta stages of Joomla 4.0. May be this causing this issue.

I have exactly the same problem on Joomla 4.0.6 running on joomla.com (CCP). Wanted to update to Joomla ‎4.1.0-rc2, but:

@b2z And does it help to apply the change from PR #35951 ?

@richard67 I thought #35951 was merged into 4.0.6 already.

@richard67 I thought #35951 was merged into 4.0.6 already.

@b2z Yes, you are right. Then I have no idea. Maybe you can see something when switching debug on in global configuration and setting error reporting to maximum and then going to the database checker (Maintenance: Database)? If you get a call stack in that case, could you post it here?

@richard67 nope. What I think it's kind of artefact of updating from Joomla 4.0 beta versions.

I'm having the same problem with a recent installation of J4.0.5 on cloudaccess.host and I haven't installed any beta versions, just J4.0.5 as it was installed for me by CCP. No extensions added. English API Id 215 is the most recent for me, too.

Hello, i have the same issue from 4.0.1 ... i several times bypass it by manual update of installation package, however after 4.1.0 the css of site was broken so i revert to 4.0.6. Any idea? I created a new empty 4.0.0 site without any additional plugin/extension and manually migrate data from 3.x site. But

Hello, i have the same issue from 4.0.1 ... i several times bypass it by manual update of installation package, however after 4.1.0 the css of site was broken so i revert to 4.0.6. Any idea?

@bonaondrej If "bypass it by manual update of installation package" means that you have just uploaded the files but not used the Joomla Update Component's "Upload & Install" method, then it is clear why the CSS was broken: With 4.1, the core templates (Atum for admin and Casiopeia for site) are changed to support child templates. This includes a database change which decides where the templates look for their assets. If you now just copy the files and maybe fix the database (which only fixes structural changes but not data changes), this data change will be missing, and so the templates will look for their assets at the wrong place.

I could provide you with an SQL statement to fix that.

But when reading "i several times bypass it", then I think your database is missing more changes.

Our documentation is very clear about that you HAVE to use the Joomla Update Component and not just copy the files.

Thanks Richard, please send me the SQL fix, a if possibly also previous i could run them in order to fix this "disabled" button.

In worst case i will do full-reinstall

Br

How shall I know which other SQL statements haven't been run? It's not a support forum here, and I do not have the time for that.

Sorry, I know that this is not a support forum. Please if possible just send me the latest.

https://github.com/joomla/joomla-cms/blob/4.1-dev/administrator/components/com_admin/sql/updates/mysql/4.1.0-2021-11-28.sql#L4

Running the SQL command fixed the admin template issue for me. But yes, I think other database changes are missing as well. I don't see the new accessibility plugin was installed, and don't see the button in my article manager. I did an upload and upgrade, and then did a "reinstall core files" I've come across this admin template issue on three upgrades on three different hosts.

On Joomla 4.1.5 fresh install I have the same issue upgrading.

On Joomla 4.1.2 same issue:

The problem is that your install did not use the joomla installer - presumably one from your web host?. You should contact your hosts and tell them this. They broke it - they should fix it ;)

Basically The schemas table is missing an entry for the version of joomla installed.

If you are on 4.1.2 then the query should be
INSERT INTO #__schemas (extension_id, version_id) VALUES (220, '[4.1.1-2022-02-20.sql];

but I already update joomla in the past without any issue.
The initial installation of joomla is by bitnami, but as I said I have already updated joomla via update and without problems.

I had the same problem and fixed it by reinstalling the Joomla core files. I was then able to upgrade the site to the next version with no issue. I wonder why this isn't being offered as a solution rather than all the technical blah blah blah and finger pointing.

@krishunt thank you for solution. Probably will save the time for others! No one offered, because no one knew how to fix it :)