User tests: Successful: Unsuccessful:
Pull Request for Issue #46308 .
Fix data type for AutoupdateRegisterState must be of type int, string given
This happens only on updated sites, because the param entry for update_status is not present in database and so the default parameter of ->get() is used.
Now the same integer default value is used like here (Unsubscribed):
Update Notification taskPHP error message in server response

Please select:
| Status | New | ⇒ | Pending |
| Category | ⇒ | Front End Plugins |
I have tested this item β successfully on f5aa259
| Status | Pending | ⇒ | Ready to Commit |
RTC
| Labels |
Added:
RTC
bug
PR-5.4-dev
|
||
β
Final test before merge with JBT recreate 5.3.3 (as for 5.3.4 composer i failed)
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-10-19 05:16:22 |
| Closed_By | ⇒ | muhme |
Thank you @heelc29 for your contribution. Thank you @richard67 and @alikon for testing.
I think after update to 5.4.0 it have many sites with locked task "Update Notification" and this block all other tasks in the Task Scheduler.
I do not know it is usefull to do
UPDATE `#__scheduler_tasks` SET `locked`=NULL WHERE `type`='update.notification';
with the next Joomla-Update-Version to fix this problem?
PR #46315 not change locked status of "Update Notification" of the Task Scheduler in the database.
I donβt think we should do that for all sites on update.
By the way, you can also unlock the locked tasks which have that running man icon by clicking on that icon.
I know this all.
But on many amateur websites the not executed Scheduler Task "Session GC" overload the database if all tasks in the Task Scheduler are blocked by locked task "Update Notification".
Other minimal solution: Information after next Joomla-Update to check the Task Scheduler of locked tasks and unlock information.
I think it is better to do anything before many amateur websites crashed with full database.
@Sieger66 I have tested this by setting up a site with 5.3 and configuring all three default scheduled tasks to run every minute.
After manually updating to 5.4.0, the Update Notification task remained stuck, while the other two tasks continued running normally.
When updating to 5.4.1 via file upload, the stuck Update Notification task fixed itself, and all three tasks ran again without any manual intervention. For my setup, this means no additional information seems necessary.
Thank you very much for your helpful comment! π
I have tested this item β successfully on f5aa259
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46315.