No Code Attached Yet bug
avatar dautrich
dautrich
25 Mar 2024

Steps to reproduce the issue

  1. Clone a site with J5.0.3
  2. Download J5.1.0_Beta2 update ZIP
  3. Start manual update by "Upload and Install" the downloaded file

Expected result

The update runs smoothly.

Actual result

The update fails (or seems to fail) with an SQL error:
grafik

The update log reveals more information:
grafik

The database needs to be repaired:
grafik

Database repair is marked as successful
grafik

Frontend and backend seem to work without issues.

System information (as much as possible)

J5.0.3
PHP 8.3.3
MySQL 8.0.33

Additional comments

avatar dautrich dautrich - open - 25 Mar 2024
avatar joomla-cms-bot joomla-cms-bot - change - 25 Mar 2024
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 25 Mar 2024
avatar alikon
alikon - comment - 25 Mar 2024

should be fixed by #42988

avatar richard67 richard67 - change - 25 Mar 2024
Status New Closed
Closed_Date 0000-00-00 00:00:00 2024-03-25 19:41:03
Closed_By richard67
avatar richard67 richard67 - close - 25 Mar 2024
avatar richard67
richard67 - comment - 25 Mar 2024

Yes, that is definitely the same issue.

Closing as already solved with #42988 .

avatar dautrich
dautrich - comment - 27 Mar 2024

I don't know whether it adds more information to the test, but I repeated the test with some more attention to update sources. When I started the update process to J5.1._beta2, there were two entries for Joomla! Core (IDs 1 and 104 in the screenshot).

grafik

For my second try, I deleted the records for update source with ID 1 from the two relevant database tables (#__update_sites and #__update_sites_extensions). After that, the update process finished without any errors.

grafik

There was no need to repair the database tables after the update anymore.

avatar richard67 richard67 - change - 27 Mar 2024
Status Closed New
Closed_Date 2024-03-25 19:41:03
Closed_By richard67
avatar richard67 richard67 - reopen - 27 Mar 2024
avatar richard67
richard67 - comment - 27 Mar 2024

Hmm, my fix was included in Beta 2, and here the update was made to Beta 2, so either the change to the SQL script made by my PR has not been applied before it was run (but it should have been), or there is still an issue with that SQL statement after my fix.

Reopening.

avatar richard67
richard67 - comment - 27 Mar 2024

I think the problem is the insert statement before the update statement which I had fixed with my PR. Will check tomorrow, and if my assumption is right I will make a PR.

avatar richard67 richard67 - change - 27 Mar 2024
Labels Added: bug
avatar richard67 richard67 - labeled - 27 Mar 2024
avatar richard67 richard67 - change - 28 Mar 2024
Status New Closed
Closed_Date 0000-00-00 00:00:00 2024-03-28 08:56:47
Closed_By richard67
avatar richard67 richard67 - close - 28 Mar 2024
avatar richard67
richard67 - comment - 28 Mar 2024

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

Add a Comment

Login with GitHub to post a comment