Skip to content

Conversation

@heelc29
Copy link
Contributor

@heelc29 heelc29 commented Oct 18, 2025

Pull Request for Issue #46308 .

Summary of Changes

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):

$registrationState = AutoupdateRegisterState::tryFrom($params->get('autoupdate_status', 0));

enum AutoupdateRegisterState: int
{
case Unsubscribe = -1;
case Unsubscribed = 0;
case Subscribe = 1;
case Subscribed = 2;
}

Testing Instructions

  • Update Joomla form 5.3.x to 5.4.x
  • Run test for Update Notification task

Actual result BEFORE applying this Pull Request

Scheduled task fails
image

PHP error message in server response
image

Task is locked
image

Expected result AFTER applying this Pull Request

Scheduled task should work
image

Link to documentations

Please select:

  • No documentation changes for docs.joomla.org needed
  • No documentation changes for manual.joomla.org needed

AutoupdateRegisterState is int enum
@richard67
Copy link
Member

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.

1 similar comment
@alikon
Copy link
Contributor

alikon commented Oct 18, 2025

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.

@alikon
Copy link
Contributor

alikon commented Oct 18, 2025

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46315.

@joomla-cms-bot joomla-cms-bot added the RTC This Pull Request is Ready To Commit label Oct 18, 2025
@richard67 richard67 added this to the Joomla! 5.4.1 milestone Oct 18, 2025
@muhme
Copy link
Contributor

muhme commented Oct 19, 2025

✅ Final test before merge with JBT recreate 5.3.3 (as for 5.3.4 composer i failed)

  • Manual updated by upload with nightly 5.4-dev, Scheduled Task 'Update Notification' fails with 'No content was returned.'
  • Second test with PRs update package and there are no more problems running the Scheduled Task 'Update Notification'

@muhme muhme merged commit 9abdd5a into joomla:5.4-dev Oct 19, 2025
40 checks passed
@joomla-cms-bot joomla-cms-bot removed the RTC This Pull Request is Ready To Commit label Oct 19, 2025
@muhme
Copy link
Contributor

muhme commented Oct 19, 2025

Thank you @heelc29 for your contribution. Thank you @richard67 and @alikon for testing.

@Sieger66
Copy link
Contributor

Sieger66 commented Dec 2, 2025

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.

@richard67
Copy link
Member

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.

@Sieger66
Copy link
Contributor

Sieger66 commented Dec 2, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants