CiviDiscount suggestions/comments

[cognoscento]

Not sure where to put these suggestions, so I'll start here and move things as appropriate.

First off, I'm really excited about the CiviDiscount extension and am thrilled at the work that Lobo, Wellebee and others have been doing to get this ready for prime time. In trying to get it working for my use case, I have a bunch of suggestions. (I wish I was a coder so that I could be more useful when it comes to these (hopefully) good ideas.

1) I've installed the v1.2 off of github into my D7/CiviCRM 4.2.2 installation. It installs fine (manually), and I can create discounts, but none of them are ever applied in the form. Any useful troubleshooting I can do on this to figure out why?

2) Going back to v1.0, I've noticed that discounts don't seem to stack together. It would be useful to be able to apply multiple automatic discounts that apply at the same time. In my case, I'm thinking a discount for being a member and a separate, but also-applied early-bird discount.

3) Adjust the UI to make the discount clearer. Maybe list the discounts(s) that apply below the prices/pricesets but before the "Total Fee(s)" line (and leave the original prices visible instead of the modified ones)? Or, less ideally, give more flexibility in formatting the message that goes after the discounted item? Being able to put "(Member Discount: 35%)" instead of (Discount: 35% for members) would make it easier to understand, I think.

Those are my immediate suggestions, which I'm sure are all much easier to suggest than implement. Are any of them easy changes?

[Donald Lobo]

We'll be announcing this as a Make It Happen later today or so. In the meantime, you can help get the ball rolling by making a contribution here:

http://civicrm.org/civicrm/contribute/transact?reset=1&id=27

Any amount large or small helps us get towards our goal.

We hope to have a better functioning discount module in the next 2-3 weeks if we make good progress with the MIH. A list of things to be addressed and fixed can be found on github here:

https://github.com/dlobo/org.civicrm.module.cividiscount/blob/master/README

This will address item 1 of your suggestion list.

lobo

[DamonKirkpatrick]

We've installed CiviDiscount on 4.2 and Joomla 2.5 and it appears to be working well.  Had to create a menu item for it but otherwise it seems to work. 

One suggestion though, it currently works with CiviMember and CiviEvent.  We'd also like it to work for CiviContribute by itself.  We sell gift certificates for memberships at holiday time.  Our purchasers are usually already members but not always and we'd like to be able to use a discount code for these gift certificates.  They don't use CiviMember or CiviEvent, just a normal contribution page with a price set. 

It seems like the discount code could be applicable based on the price set used for the page.

Any chance this could get included in the MIH?

Thanks,

Damon

[Donald Lobo]

Yes, i think we should be able to add this feature if/when the MIH gets closer to its goal.

Since your org is using CiviDiscount, would really help if your org can make a generous donation towards the MIH

lobo

[DamonKirkpatrick]

Done.  Not much but hopefully it helps!  Thanks for all your hard work!

[Donald Lobo]

Hey Stoic:

thanx a lot for your generous donation We do hope to release a new version of this module with this feature request and a bunch of things that keithm did and supported in the next few weeks

lobo

[jsimonis]

I see we're getting pretty close on the MIH. I'm hoping to be able to make a contribution myself in the next few weeks. Won't be a lot since I don't have a company or organization behind me (plus Christmas is approaching), but I'd like to kick in something for this.

I plan on installing the latest version here in the next day or so. Is there anything I need to know with regards to going from the version I have installed now (the one previously listed as stable) and the latest version?

Thanks everyone!

[DamonKirkpatrick]

The only hiccup I encountered was the menu problem (well, that and I assumed it would work the way I wanted it to because I didn't read the documentation clearly enough ) . I did notice on the demo site that the discount code field appears way near the top of the contribution page and is not really in an intuitive spot.  Seems an easy enough fix though.  Otherwise, it seemed to work fine for memberships and events.  I created my own codes and it worked properly.

[jsimonis]

Great to hear. I'd been planning to use css to move the field for now, as I agree with you about it being in a weird spot. Most people expect it to be near the price and/or payment info.

[jsimonis]

Ok, I uninstalled the old version and installed the new version. I'm using CiviCRM 4.2 on Drupal 7.

I created a discount code to test, which was attached to a membership type. I went to that membership signup page, inputted the discount code, and hit apply. I get this on the next page:

Sorry but we are not able to provide this at the moment.
HTML_QuickForm_Controller: Unhandled action "reload" in page "Main"
Error Details
Additional Details:
Array
(
    [callback] => Array
        (
           

• => CRM_Core_Error
[1] => handle
        )

   

Code: [Select]

=>
    [message] => HTML_QuickForm_Controller: Unhandled action "reload" in page "Main"
    [mode] => 16
    [debug_info] =>
    [type] => PEAR_Error
    [user_info] =>
    [to_string] => [pear_error: message="HTML_QuickForm_Controller: Unhandled action "reload" in page "Main"" code=0 mode=callback callback=CRM_Core_Error::handle prefix="" info=""]
)
Return to home page.

[Kurund Jalmi]

You might have to use CiviCRM v4.2 from svn ( or wait for next 4.2.x release )

Kurund

[jsimonis]

We're just using 4.2 right now - work it work better if I grab one of the newer 4.2.x versions?

[Donald Lobo]

u'll need to update from svn or wait for 4.2.7 (which most likely will be out the week after thanksgiving)

lobo

[jsimonis]

Thanks. I need to show them in the next few days that it works, so I'll go ahead and grab it from svn.

[jsimonis]

This is the first time I've updated via svn. Do I need to use a branch version or the trunk?