Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I am using Rules Scheduler to do routine tasks on my site. It would be great to be able to not execute the rule if the site is in maintenance mode. I checked under data comparison and didn't see a way to easily test this variable. Is there a way to do this currently w/o using PHP, or should I make this a feature request?
Comment | File | Size | Author |
---|---|---|---|
#11 | 1719572-10-maintenance-mode.patch | 6.84 KB | TR |
#8 | 1719572-8.patch | 4.13 KB | TR |
#6 | 1719572-6.patch | 4.02 KB | TR |
#3 | 1719572-3.patch | 4.01 KB | TR |
|
Comments
Comment #1
TR CreditAttribution: TR commentedIf someone wants to contribute a patch to implement this, I'm willing to take a look at it.
Comment #2
TR CreditAttribution: TR commentedThis is likely to need #2840815: Support custom Conditions that don't need context
Comment #3
TR CreditAttribution: TR commentedNow that #2840815: Support custom Conditions that don't need context has been committed, we can implement this new feature.
Here is a patch with a new condition to test if the site is in maintenance mode, as well as a unit test for this condition.
Please review.
Comment #4
TR CreditAttribution: TR commentedComment #5
TR CreditAttribution: TR commentedActually, since there has been absolutely NO interest from the community since this feature request was made back in 2012, I'm going to add this as a feature to my own project.
Comment #6
TR CreditAttribution: TR commentedRe-rolled patch for new namespace.
Comment #8
TR CreditAttribution: TR commentedComment #9
rodmarasi CreditAttribution: rodmarasi commentedfollowing your work on Rules and Rules essentials. thanks for the efforts
Comment #11
TR CreditAttribution: TR commentedPatch relies on features in Rules 8.x-3.x-dev, while the testbot only will test against Rules 8.x-3.0-alpha4. So we have to make the patch backwards compatible until the next Rules alpha is released.
Comment #14
TR CreditAttribution: TR commentedOK, those are the two current (expected) branch failures. Not related to this patch. Committed.
Comment #15
TR CreditAttribution: TR commented