Package: mezzanine-seminars
Mezzanine SeminarsSeminar platform forMezzaninesites.FeaturesCreate seminars with public and private contentAccept payments to grant users access to seminarsUse registration codes to give access to select user groups without paying"Subject" (category) system to group seminars by topicAllows attendees to fill out "post-seminar surveys" to provide feedbackCSV exports of seminar registrationsChangelog / History / Release NotesCheck outGitHub Releases.InstallationInstall via pip:pip install mezzanine-seminars.Add"mezzanine_seminars"toINSTALLED_APPS. Make sure"mezzanine.accounts"is also added.Add to your rooturls.py:url("^seminars/",include("mezzanine_seminars.urls",namespace="seminars"))A new Seminars section will appear in the admin. Create your first Seminar!Point your visitors to/seminars/to see the list of available seminars.Accepting paymentsBy default registering for a Seminar is completely free even if the seminar has a set price. You can enforce a payment requirement by using a custom form insettings.SEMINARS_REGISTRATION_FORM. Different payment processors require different forms:StripeFirst, make sure you install the additional requirements withpip install mezzanine-seminars[stripe]. Then make sure you define your secret API key insettings.STRIPE_SK. In development this should be a test key.Finally set the Stripe form to be used when users register for a seminar:# settings.pySEMINARS_REGISTRATION_FORM="mezzanine_seminars.forms.stripe.StripeRegistrationForm"This will handle the backend configuration, but you will need to overrideseminars/seminar_registration_create.htmlto configure Stripe's browser bindingsstripe.js. This is explained inStripe's official docs, but it boils down to sending a PaymentMethod ID in the hidden field namedstripe_method. With that the server will be able to complete the purchase.Registration CodesSome users might pay for seminar access without using the website, or you (the site owner) might have a special agreement with them to give them access to seminar content without paying. Registration Codes let you do this. Here's an example:ACME Inc. has reached an agreement with you for 20 seats for Seminar XYZ. Site admins create the Purchase Code "acme" with the capacity limited to 20. Employees of ACME Inc. will now create their own accounts on the site and enter code "acme" during the registration step for Seminar XYZ instead of paying for their registration. Once the code has been used on 20 registrations it is no longer valid. Site admins will be able to see which code was used in the Seminar Registration admin to identify the 20 attendees from ACME. Multiple Purchase Codes can be active at the same time to allow enrolling multiple user groups, each with a set number of seats.Generally you will want to combine Registration Codes with an alternative payment method to give users a choice of which to use. For this reason the formmezzanine_seminars.forms.BaseRegistrationCodeFormis provided to be mixed in with other forms.For example, to allow users to register with Stripe OR Registration Codes:# your_app/forms.pyfrommezzanine_seminars.formsimportBaseRegistrationCodeFormfrommezzanine_seminars.forms.stripeimportStripeRegistrationFormclassCombinedRegistrationForm(BaseRegistrationCodeForm,StripeRegistrationForm):"""Seminar Registration form that supports both Stripe and Registration Codes"""# settings.pySEMINARS_REGISTRATION_FORM="your_app.forms.CombinedRegistrationForm"ContributingBefore you contribute a bugfix or add a new feature, please check the issue tracker and open a new issue to discuss the work to be done. Once you're clear you want to work on the codebase:gitclonegit@github.com:unplugstudio/mezzanine-seminarscdmezzanine-seminars# Test suitepipinstall-e.[testing]pytesttests# Code stylepipinstallflake8black
flake8.
black.# ALTERNATIVE: have Tox run everything (tests and code style)pipinstalltox
toxOnce you're done with your changes and ensured all tests pass, create a pull request and verify the continuos integration tests also pass.