stfinney / ffx Goto Github PK

The Organizer field was originally just set as a foreign key field, which meant the admin form provided a drop down selector with the options being all the registered users. This is not ideal, as the author of an event would have to find themselves on a potentially long list, and it also leaves it open to malicious mis-attribution of events. Currently, the field is set to non-editable to avoid this issue, but what it really needs is to default to the current user when they create an event (and still be non-editable, so there's no room for mistakes or deliberate mis-attribution).

It currently does nothing, so hook that up!

We need to figure out how to enable User registration for the site, and then do it. This task would also include getting a login form working, and initial pass at a framework for having pages that require the user be authenticated.

First pass functionality for logged-in users to register for Events from the detail page.

Initial implementation should just be a print out of all the data for an Event that is intended to be publicly viewable. No template/styling necessary at this stage.

Should the user be part of an "organizers" group? How do we establish that the user is an organizer?

Starting with a plain list of all upcoming events, we need to create the main View of the Event data. We can iterate on that to add filtering/searching/etc.