It appears that ubercart roles stores an expiration date but doesn't (without a patch) make the expiration date available to views.

The role expire module seems to interface with views and rules but it's expiration date isn't automatically set by ubercart.

So, I'm wondering whether it makes sense for ubercart users to use both modules and to provide better integration between them or whether it makes more sense for the solution to stay within ubercart and to replicate some of the same functionality.

In particular, a common requirement seems to be to have at least one, if not several reminders about roles that are about to expire or that have already expired.

Any thoughts on this?

Thanks.

Comments

longwave’s picture

It makes sense to better integrate with Role Expire; there is no point maintaining two similar sets of code in different projects. Ubercart originally shipped with uc_roles before Role Expire even existed, and this remains for backward compatibility - in Drupal 8 it would be nice if we can remove uc_roles if similar functionality is available in contrib, but we cannot do this now in Drupal 7 as it would remove working functionality for existing users.

Better integration could be done in Ubercart core, or in a contrib glue module that helps Ubercart work better with Role Expire - I'm not sure if such a thing already exists or not.

Patches, as always, are welcome to improve the situation with this or any other feature.

jsibley’s picture

It appears to be possible to add an expiration date to Role Expire using rules.

Not sure if this is helpful, but could be at least an interim solution.