- last update
almost 2 years ago Patch Failed to Apply - last update
almost 2 years ago Patch Failed to Apply - Status changed to Needs review
over 1 year ago 3:17pm 16 October 2023 - last update
over 1 year ago 31 pass, 1 fail The last submitted patch, 62: ultimate_cron-n2692781-62.patch, failed testing. View results →
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.- last update
over 1 year ago 15 pass, 10 fail - 🇺🇸United States DamienMcKenna NH, USA
This should fix the info file problem.
The last submitted patch, 64: ultimate_cron-n2692781-64.patch, failed testing. View results →
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.- last update
over 1 year ago 32 pass - 🇺🇸United States DamienMcKenna NH, USA
@super_romeo: The settings form is saving correctly for me, could you please try again?
Does this need more tests? Or is this enough?
- last update
about 1 year ago 34 pass, 2 fail The last submitted patch, 68: ultimate_cron-n2692781-68.patch, failed testing. View results →
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.- 🇨🇭Switzerland berdir Switzerland
Converted to a merge request and fix tests, but once again, I'm not convinced by what I see here.
Fundamentally, the whole thing still doesn't do anything. The default values are not used when creating new jobs. And this still does change the configuration structure of jobs, which would break existing configuration. Untangling that would require quite a bit of work.
Instead, I created 📌 Remove unused global settings forms and other dead settings plugin classes Active as an intermediate step to unblock the beta release.