No Code Attached Yet Information Required bug
avatar msauer75
msauer75
31 Jan 2023

Hi,
I did an upgrade from Joomla 3.10 to the latest 4.2.6. Now I will get this error Column 'checked_out' cannot be null.
What can I do?
BR
martin

avatar msauer75 msauer75 - open - 31 Jan 2023
avatar msauer75 msauer75 - change - 31 Jan 2023
Labels Removed: ?
avatar joomla-cms-bot joomla-cms-bot - change - 31 Jan 2023
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 31 Jan 2023
avatar chmst
chmst - comment - 31 Jan 2023

First go to system - information and check if your database is up to date. Maybe you need to repair it

avatar msauer75
msauer75 - comment - 31 Jan 2023

I checked:
image

avatar richard67
richard67 - comment - 31 Jan 2023

@msauer75 The change of the checked_out columns to allow NULL values is made here: https://github.com/joomla/joomla-cms/blob/4.2-dev/administrator/components/com_admin/sql/updates/mysql/4.0.0-2020-05-29.sql#L31-L49

In the update log "administrator/logs/joomla_update.php" the execution of these SQL statements and the file name "4.0.0-2020-05-29.sql" should have been logged during the update like in the following example:

Ran query from file 4.0.0-2020-05-29.sql. Query text: ALTER TABLE #__extensions MODIFY checked_out INT UNSIGNED;

Could you check and report back if this is the case?

And check the fix suggested here: https://forum.joomla.de/thread/15460-1048-column-checked-out-cannot-be-null/?postID=103577#post103577 .

Thanks in advance.

avatar Quy Quy - change - 1 Feb 2023
Labels Added: Information Required
avatar Quy Quy - labeled - 1 Feb 2023
avatar Hackwar Hackwar - change - 22 Feb 2023
Labels Added: bug
avatar Hackwar Hackwar - labeled - 22 Feb 2023
avatar richard67
richard67 - comment - 6 Apr 2023

@msauer75 Have you checked my previous comment? Could you check as advised there and report back?

avatar msauer75
msauer75 - comment - 11 Apr 2023

Hi,
I changed the column to the following
image

avatar richard67
richard67 - comment - 11 Apr 2023

@msauer75 This doesn’t really answer my questions.

avatar brianteeman
brianteeman - comment - 1 Aug 2023

In the absence of any follow up can only assume that the problem has been resolved. In every case that this error has been reported it has been related to an upgrade failure.

Dont see what else can be done here and it should probably be closed.

avatar alikon alikon - change - 2 Aug 2023
Status New Closed
Closed_Date 0000-00-00 00:00:00 2023-08-02 07:11:21
Closed_By alikon
avatar alikon alikon - close - 2 Aug 2023

Add a Comment

Login with GitHub to post a comment