Closed (fixed)
Project:
Commerce userpoints
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
13 Nov 2011 at 12:06 UTC
Updated:
19 Jan 2013 at 21:20 UTC
I've started working on a common commerce_userpoints module.
The main thing that it does is give you the ability to set up a currency for each userpoints category, including the ability to use a custom name, code and symbol for it.
This is already working pretty well, I'm currently updating the discount points selection widget on top of it (including information about exchange rate and stuff) but then the Skyrim download finished and progress stalled a bit ;)
Will post some code and screenshots soon.
Comments
Comment #1
dabblela commentedSub
Comment #2
BenK commentedHey Berdir,
Long time, no talk! This is very interesting stuff... I just discovered the project. Will take a closer look....
--Ben
Comment #3
Taxoman commentedAnother module, not this http://drupal.org/project/commerce_userpoints ?
Why not add such seemingly relevant features to this one?
Comment #4
berdirIn case you didn't notice, this issue is part of that project ;)
The module in this project is called commerce_userpoints_discount and is specifically about displaying a checkout pane that allows to use points for a certain (can be all) amount of the order amount. There are other possible use cases for integration between userpoints and commerce, see #1268564: Support additional use cases.
The goal for the base module is to provide common feature to all of these, which will live in separate modules so that you only have to enable those that you want to use.
Need to get back to this, haven't found the time.
Comment #5
Taxoman commentedThanks for the quick reply.
Yes, I know it is this issue queue, but the formulations led me to assume that it was about another module, but no name given, and no link - so will it be a sub-module of this one, is that the point? (and it does not exist "anywhere" yet?)
Comment #6
berdirIt exists in my local git repository ;)
The other way round. The new module will be the base module and the existing discount module will be sub-module (not really sub-module, but based on it).
Comment #7
Taxoman commentedok, so is "the existing discount module" referring to _this_ one, so that in the end there will be 2 modules in total related to this?
Will _this_ one then have a dependency, requiring the new module?
Comment #8
berdirThis *project* will contain two *modules*, where commerce_userpoints_discount has a dependency on commerce_userpoints. Yes.
Later, additional modules will be added, for example one that allow to buy userpoints and a real payment_method. All of these will depend on the base commerce_userpoints module.
Comment #9
play4quarters commentedVery interested in this.
I was wondering, in the meantime, if it were possible through rules, to issue coupons in exchange for userpoints, and then allow the member to utilize that personalized coupon in the store?
Does this seems like a doable workaround?
Thanks!
Comment #10
berdir@play4quarters: This project already contains a module that can be used for discounts through userpoints. The purpose of this issue is to refactor it to make it more flexible and allow different use cases as different modules.
Comment #11
play4quarters commentedThanks Bedir.
I had thought I had read that there were issues in terms of synching with what points were available or not available...I'll give this a much closer look.
Thanks for the direction.
Comment #12
orendain commentedHey Berdir - any update on the base module? I'd love to take a look and see about helping develop modules for the other use cases.
Comment #13
mrfelton commentedHave incorporated some of Berdir's work on creating a commerce_userpoints module to contain common functionality. Check 7.x-1.x branch.
Comment #14
a.ross commentedThat looks interesting. Are there any issues in upgrading from previous version? Also wondered if you could review some of the UI enhancements we made here:
http://drupal.org/sandbox/gdarends/1787934
Thanks