-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Private Donation Checkbox #83
Comments
Good work team. |
👍 thank you! |
Great to see this make it into the plugin! When I did a crowdfunding project I was surprised to see over 25% of the donations were anonymous. It's an important thing to add! |
👍 This is definitely a must for charities. A lot of people do not want their left hands know what their right hand is doing. @DevinWalker , Is there a method already to display the donor's list in the front end (like for example: http://www.gofundme.com/uenr3b2a ) ? I don't see a requirement for this feature unless we are displaying the donors list in the front-end. |
We have a Gravatar list functionality that I want to expand into a widget similar to: So this feature will definitely be a requirement |
I'm removing this from the 1.0 milestone and adding it to the 1.1 |
Pushing out again to 1.2 |
Let's make this a priority soon. Really very often requested. |
Yeah I agree it needs to be out soon. |
Hate to do this... but I gotta push this milestone again. |
Duplicate, closing in favor of #17 |
* chore: Update test to assert array subset, not same * refactor: remove getId and getName methods from form template contract in favor of static methods * refactor: remove classic template js file in favor of AmountField in core * chore: Remove unecessary template script * chore: Add type for form templates * refactor: remove unused dependencies method from classic and dev templates Co-authored-by: Jon Waldstein <jonwaldstein@macbook-air.mynetworksettings.com>
Add a checkbox during donation payment process that requests a donation be private (not displayed at all on frontend).
The text was updated successfully, but these errors were encountered: