4.1.5 has the same issue

@tecpromotion Could you advise here about checking the schemas table? I have to go to the office so I don’t have time before tonight.

"4.1.5 has the same issue" Ditto..

Can't replicate on J4.2.1 rc3

I cannot replicate on different sites.
@rganeyJ have you error-reporting on maximum and debug-mode "on"? Which PHP version?

I have heard about this problem mainly from people who have used a custom installer from their hosting provider. If @tecpromotion who also knows about these issues is not faster, I can provide tonight a database query for further investigation. Please be patient.

the problem occurs when there is no record in the #__schemas table and without this record its impossible to update joomla in the future

This will occur if the custom installer blindly assumes that everything is in the sql file - its not. This is NOT a problem from Joomla but it is a problem created by the custom installer.

As a super quick fix (and this is NOT the correct way but it works for you until @richard67 can review)

In the #__extensions table find the extension_id of "files_joomla"

Insert a record in the #__schemas table with the extension_id from above and 1 for the version_id

Now go back to the database page on your website. It will show the record and (because of the incorrect version) will say there is stuff to fix. Click on the update structure button and you're good to go.

Tagging cloudaccess so they can fix their installer @jonathanCA @Pawel-Panek @DSniegu

Please check the content of the #__schemas table in PhpMyAdmin and make a screenshot and post it here before you follow Brian’s good suggestion above so I can see if the record is completely missing or if it is there but with a wrong id.

@richard67 I had seen this before with another host and their own custom installer which I helped to fix. They just took configuration.php-dist and ran the sql. That works to a point and thats why they didnt see any problem. But as we cvan see that of course creates problems

Yes, I understood. Am thinking about working on a fix to make the database checker more resilient for this and making it possible to fix that with the “Update Structure” aka “Fix” button because that error keeps people from updating.

@richard67 I wouldnt waste time on that. The host created the problem. Once aware they should fix it.

@brianteeman yes you are right with "The host created the problem" but if Richard finds a good solution, then we all benefit.
I know at least two hosters who could benefit from this. And maybe something will come back from them as well.

@brianteeman @richard67 is there any way we can run ConfigurationModel::setup() via Joomla CLI https://github.com/joomla/joomla-cms/blob/4.2-dev/installation/src/Model/ConfigurationModel.php#L49?

The reason I'm asking is this procedure can change anytime and if we attempt to code it outside of Joomla it eventually become wrong again.

if we attempt to code it outside of Joomla

@Pawel-Panek Why do you want to do that?

@richard67 so that they can install joomla unattended

@Pawel-Panek probably not at the moment. @Hackwar is working on a cli installation script but no idea if/when that will be released.

The reason I'm asking is this procedure can change anytime and if we attempt to code it outside of Joomla it eventually become wrong again.

Not for me to tell you how to do your job but there is nothing new about this afaik.

@brianteeman yes you are right with "The host created the problem" but if Richard finds a good solution, then we all benefit. I know at least two hosters who could benefit from this. And maybe something will come back from them as well.

actually we dont benefit at all. of course we can write some code to allow a user to fix this specific problem but who knows what other problems are created by installing joomla for a customer this way. As this is an easy to see error I would prefer it if we dont offer an easy way for a user to fix it and instead get the hosts to check their entire scripting

@richard67 yes, unattended install - this is what we need.

I'll reach out to @Hackwar to see how can we help. For the moment we will use the code from setup function.

@Pawel-Panek you can see what he is working on here #38325

@brianteeman

the problem occurs when there is no record in the #__schemas table and without this record its impossible to update joomla in the future

This will occur if the custom installer blindly assumes that everything is in the sql file - its not. This is NOT a problem from Joomla but it is a problem created by the custom installer.

As a super quick fix (and this is NOT the correct way but it works for you until @richard67 can review)

In the #__extensions table find the extension_id of "files_joomla"

Insert a record in the #__schemas table with the extension_id from above and 1 for the version_id

Now go back to the database page on your website. It will show the record and (because of the incorrect version) will say there is stuff to fix. Click on the update structure button and you're good to go.

This fixed one thing and brock another lol. By adding the record the system then properly allowed me to 'fix" the database. however now the admin and site template is not loading.

I am looking into that now, I am not a power user so it will be a bit. Thanks and it looks like it is associated with the autoinstaller they are using.

@rganey This is something that @Pawel-Panek at CloudAccess should help you fix. They broke it

@brianteeman thanks.

@richard67 I wouldnt waste time on that. The host created the problem. Once aware they should fix it.

thats not entirely true. My install is NOT a host install
Richard and I have been over mine once before.

@rganey I updated you over the ticket.

@N6REJ well it wont be the first time that you have had a messed up install

This can be closed now. The issue with cloudaccess is presumably resolved or in the process of being resolved and there is nothing more to do here.

@N6REJ well it wont be the first time that you have had a messed up install

kiss off @brianteeman

So, because its "ME" agreeing with the issue, it can't possibly be a valid issue

@brianteeman @richard67 the site provisioning issue has been mitigated. We'd be better off with CLI installer but anyways it works now. The CLI improvement is in progress and that's great. We'll certainly use it once it goes to stable.

@Pawel-Panek Thanks for the update.