After removal of a PHP version, the panel displays the correct higher remaining version in cronjobs, but internally, the jobs still reference files of

[Bitpalast]

Username:

TITLE

After removal of a PHP version, the panel displays the correct higher remaining version in cronjobs, but internally, the jobs still reference files of the removed PHP version

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

18.0.81 latest MU

PROBLEM DESCRIPTION

A cron job was set to use PHP 7.4.
PHP 7.4 was removed.
The end user now sees "8.3" in the PHP version selection of the cron job.
However, internally, the job still references the binaries of the removed PHP 7.4, hence it throws an error when executed. This happens when you hit "run now" from the cron job list, but it does not occur when you hit "run now" on the cronjob detail page.
Solution was to actually store the affected jobs again once, so that the correct PHP version is set.

STEPS TO REPRODUCE

1. Set a cron job to use any PHP version.
2. Remove that version.
3. Hit "run now" from the cron job overview page.

ACTUAL RESULT

On the cron job detail page, the drop down list is set to the next available higher PHP version.
In reality in the background, the PHP version was never changed.
An error is thrown when you hit "run now" from the cron job overview page while the job correctly runs with the now loweste available PHP version on the cron job configuration page.

EXPECTED RESULT

Removal of a PHP version should update the cron jobs to the next higher available version so that the version display and the actual PHP version stored in the job file are in sync.

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug