liz4v / esupa

Event Subscription and Payment (Django App)

Esupa

Esupa is an inactive free software licensed under the Apache License meant to handle collection of attendee data and payment for events that are just big enough for Google Forms and manual deposits being insufficient.

It's created for Abando, an annual event in Brazil, in the hopes that this can be universally useful.

The name stands for Event Subscription and Payment.

Installation

• Python 3
• pip3 install django django-pagseguro2
• django-admin crateproject <project-name>
• cd <project-name>
• git clone https://bitbucket.org/abando/esupa.git
• Add esupa to your project's INSTALLED_APPS and urls.py
• manage.py compilemessages (optional; only needed for localization)

Usage

You must set up a registration and authenticiation application. Just django.contrib.auth does the job, but I use django-oneall.

Then use the Django Administration panel to create a new Event. Make sure to set its date in the future.

After this is set, you can navigate to the main page and you will see the main subscription page.

Roadmap

• Have each Event have its own staff list, deal with permissions based on that. Some with read permissions only.
• Add support more payment processors. Payza? BCash? Moip?
• Localization of optionals and other database-stored strings.
• Flesh out partial payments. How should new expiry dates be calculated?

Authors

Ekevoo only, but heavily based on plenty of discussions and advice from WhiteRaccoon, who really helped mature the ideas while working hard at the PHP predecessor of this.

esupa's Issues

Json status

Have a way to provide the capacity occupation status from an outside site. Proposed format:

URL: /event_slug/json/state

{"exists": true,
 "id": 1, "slug": "abando9",
 "subs_open": true,
 "currently_available": 10,
 "potentially_available": 15}

{"exists": true,
 "id": 1, "slug": "abando9",
 "subs_open": true,
 "currently_available": "over 20",
 "potentially_available": "over 20"}

{"exists": true,
 "id": 2, "slug": "abando10",
 "subs_open": false}

{"exists": false,
 "slug": "does not exist"}

The upper bound is configurable from the event edit screen from Django admin panel.

Bank Deposit information missing or not in a proper place

Users are complaining that Bank Deposit information is missing. It might only being visible when clicking "Deposit" (expected).

Users expect to see the bank information right away, before click in "Deposit" to attach their photo.

Makes sense, because system creates a new Payment Intent to every person that just want to get the bank information, then they will create another one later on. We can circumvent that by displaying the information right away.

Implement per-event staff list for permissions.

Currently permissions are being controlled by User.is_staff : bool. That's no good.

PagSeguro receives 500 error when calling back ESUPA

When a payment status changes in PagSeguro, the system doesn't get updated. It has to be performed manually.

How to reproduce:

• Create a new payment
• (System will receive a new billing from PagSeguro as expected)
• PagSeguro changes its status (success or cancelled)
• ESUPA throws 500 to PagSeguro

Decimal values should not require the fractional part

Try to fill a partial payment value without including the cents and it will fail. Should assume zero cents.

Take the custom makeesupamessages command out, somehow.

Most messages are silently disappearing when makemessages is run for other purposes. This is becoming a mantainability nightmare.

Best bet so far seems to be: https://pypi.python.org/pypi/django-extra_keywords