- Issue created by @bojan_dev
- Status changed to Needs review
9 months ago 5:19am 3 September 2024 - 🇬🇧United Kingdom aaron.ferris
+1 for this change. Attaching a patch from the MR.
- 🇬🇧United Kingdom aaron.ferris
Needs some thought on how we approach this, given this module is already out in the wild. Perhaps we need this behind some sort of toggle, so that the module will continue to behave as it currently is (cron settings from config) but can be overridden with a checkbox.
- 🇳🇴Norway steinmb
+1 from me. Perhaps make the change to only 3.x, avoiding potential breaking sites with exiting functionality?
- 🇬🇧United Kingdom aaron.ferris
aaron.ferris → changed the visibility of the branch 3471724-remove-cron-frequency to hidden.
- Merge request !22Issue #3471724: add option for bypass export frequency interval → (Merged) created by aaron.ferris
- 🇬🇧United Kingdom aaron.ferris
Ive decided to take a slightly different approach to this, by adding another option in the interval select.
This should give the best of both worlds. We now have
1. Never - self explanatory
2. List of intervals - the way the module has historically worked
3. Bypass - which leaves the cron configuration open, but will ignore any time based interval, so that it can be used with Ultimate Cron and the likesFeedback/testing welcome.
- 🇧🇷Brazil brandonlira
Hi @aaron.ferris,
I manually tested MR !22.
- Selected "Every Cron run" in the configuration form.
- Triggered cron multiple times manually.
- Confirmed that the synonym export was executed on each cron run.
Verified that the following messages appeared in the logs:
- Executing export
- Export for English complete
Confirmed expected behaviour without requiring a time-based interval.
Looks good to me.
Thank you! -
aaron.ferris →
committed 19726ecc on 3.0.x
Issue #3471724: add option for bypass export frequency interval
-
aaron.ferris →
committed 19726ecc on 3.0.x
Automatically closed - issue fixed for 2 weeks with no activity.