Edit live events data + tickets

[thomasweld]

Ability for the owner to edit an live event.

Create two different edit options -

1. Simply edit event details - time, date, image, description, title..etc
2. Edit tickets.

If the user wants to edit tickets:

Create a model that stores tickets that are on hold or already sold and separates them from the editing process. After the user makes their changes and clicks save, the existing tickets are updated or deleted based on the changes made by the user.

-- OR --

If user edits tickets all existing tickets available for sale are deleted and re-created based on the changes made by the user. The existing tickets that have been sold or are on hold can be held in a completely separate database, essentially creating multiple ticket tables that can be associated with each event.

[kyledcline]

Ticket alteration moved to #1, requires state machine to avoid conflicts and errors.

For now, we can allow event modification via event dashboard and just allow basic fields to be altered.

[kyledcline]

This should include a tinymce (or some other WYSIWYG) editor embedded into event description and this should be marshalled into the database safely.

[roman-raizen]

I've added tinymce, fixed some abilities, refactored abilities and made events editable.

If you agree, I could work on tickets edition and properly role setting.

[kyledcline]

Push up what you have so we can close this issue, please. We're using standard pull requests method. Checkout a new branch, commit changes in large, functional commits, then push and request a pull.

[kyledcline]

Tied to issue #13.

[roman-raizen]

I've pushed it to edit_events_data branch

[kyledcline]

Did you see my comment on how to create a pull request?

We shouldn't rely on branch pushes for merge notifications.