- Issue created by @Gabbia998
- First commit to issue fork.
- 🇮🇳India dineshkumarbollu
Hi the property of $last_run is private can provide more info on this.
Thanks
- 🇫🇷France arnaud-brugnon
Here's a patch to solve this.
But i really think that private should be changed as protected.
- Status changed to Needs review
over 1 year ago 7:16am 3 April 2023 - 🇩🇰Denmark larsmw
Hi,
This seems like a duplicate issue of this https://www.drupal.org/project/ultimate_cron/issues/3370283 🐛 CronRule.php does not handle all variables properly RTBC - which is related to a similar 7.x issue.
- last update
about 1 year ago 25 pass, 4 fail - last update
about 1 year ago 31 pass, 2 fail - Open on Drupal.org →Core: 9.5.x + Environment: PHP 7.3 & MySQL 5.7last update
about 1 year ago Not currently mergeable. - @rishabjasrotia opened merge request.
- last update
about 1 year ago 32 pass - 🇺🇸United States DamienMcKenna NH, USA
This is a duplicate of 📌 Fix PHP 8.2 deprecation issue with CronRule-class RTBC , which also adds a docblock comment. But I also just noticed there's a class variable defined called $last_run, but then the rest of the code uses $this->last_ran, so this ultimately was a typo.
- last update
11 months ago 25 pass, 4 fail - Status changed to Closed: duplicate
10 months ago 10:22am 3 February 2024 - 🇮🇳India aadeshvermaster@gmail.com
Patch #4 works for me. I am using ultimate_cron version 2.0.0-alpha6
@aadeshvermaster@gmail.com, just update to 2.0.0-alpha7 and you won't need the patch anymore.