Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduler Web Cron is capturing the article id instead of the task id #43154

Closed
uGE70 opened this issue Mar 25, 2024 · 6 comments
Closed

Scheduler Web Cron is capturing the article id instead of the task id #43154

uGE70 opened this issue Mar 25, 2024 · 6 comments

Comments

@uGE70
Copy link

uGE70 commented Mar 25, 2024

Steps to reproduce the issue

  1. Check that your website is using a Joomla article as the home page in your main menu (with an article id).
  2. Copy the basic Scheduler Web Cron link and paste it in any browser: https://www.domain.com/component/ajax/?plugin=RunSchedulerWebcron&group=system&format=json&hash=hashstring
  3. In file /plugins/system/schedulerunner/src/Extension/ScheduleRunner.php, var_dump the result of line 205:
    $id = (int) $this->getApplication()->getInput()->getInt('id', 0);
    var_dump($id);
    exit;

Expected result

I should get id=0 and the task scheduling should work properly without any additional id parameter.

Actual result

I get the current homepage article id. Adding &id=0 in the web cron link is solving the issue.

System information (as much as possible)

Joomla 5.0.3 / 4.4.3, PHP 8.2 or less. Infomaniak shared hosting (task planner).

Additional comments

Thanks for your much appreciated work

@Hackwar
Copy link
Member

Hackwar commented Mar 26, 2024

Can you take a look at #42989 and see if this fixes your issue?

@uGE70
Copy link
Author

uGE70 commented Mar 26, 2024

Hello,
Thanks for your message.

@Hackwar
Copy link
Member

Hackwar commented Mar 26, 2024

Thank you. I'll have a look what can be done here.

@Hackwar
Copy link
Member

Hackwar commented Mar 26, 2024

Can you check #43164 if that helps you?

@uGE70
Copy link
Author

uGE70 commented Mar 26, 2024

Hello,
Thanks a lot for your work. I've applied the patch and now it's working as expected.

@Hackwar
Copy link
Member

Hackwar commented Mar 26, 2024

Then please comment accordingly in the PR. I'm closing this issue now, since we have that PR.

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

No branches or pull requests

4 participants