Rather than using a fixed number of redemptions, we have clients that would like to specify the start and end date for the 'life' of a coupon, so that it is automatically available between these 2 dates, and it is no longer available after the expiration date.

Would this be a difficult feature to add?

CommentFileSizeAuthor
#2 uc_coupon.install.patch603 bytesdbh01
#2 uc_coupon.module.patch4.53 KBdbh01

Comments

dbh01’s picture

dbh01 commented

I've actually added this, to my own version of uc_coupon. After the code goes into production for my client, then I'll provide a patch and send it to the package maintainers. Longwave already knows this is on the way.

dbh01’s picture

dbh01 commented
Assigned: Unassigned » dbh01
Status: Active » Needs review
StatusFileSize
new uc_coupon.module.patch4.53 KB
new uc_coupon.install.patch603 bytes

Attached are the patches for adding a start date to uc_coupon
this is based on the latest 6.x-1.x-dev code

longwave’s picture

longwave
he/him
Primary language English
Location UK
commented
Status: Needs review » Fixed

Committed to 6.x branch, thanks for the patch!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
commented

I have a need for an hour granularity. I'll work on this myself and submit a patch.