Currently, it seems that when the "time left" for a file has elapsed, the status of the file still shows "Active". Should the status update (via a rule) to show "Expired" instead?

Thoughts?

--Ben

Comments

recrit’s picture

I agree there needs to be some sort of status change for "expired". I need to add a status for this - currently only active, pending, and canceled is in the module now.

To control the status, the rules that would be needed:
[1] Download request - exists already - control access and perform an action if allowed
[2] Download access denied - exists already - fires when request event rules fail
[3] Log download - exists already but might turn into "on download complete" then just do log action on download complete.

The access denied event would only give the opportunity to make sure the status was "expired", but it would be nice to have then initial status change happen when the limits are reached, ie after last allowed download. The problem here is that the [1] access control is flexible enough that it could be more than limit based or not limit based at all, so the only way to know is if the [1] rule denies access.

thoughts?

bojanz’s picture

Version: 7.x-1.x-dev » 7.x-2.x-dev
Status: Active » Fixed
Issue tags: +possible-backport

I have published 7.x-2.x (see https://drupal.org/node/1395488#comment-7658191) which relies on commerce_license, which has expiration code that runs on cron. So marking this as fixed, and marking for possible backport.

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