I generated the Administration section using Forge and tried to use it. Here are some issues I've found:

1. It is possible to create new event or venue without any Media Item, but then the detail of event or venue in administration doesn't work and the "Events" and "Venues" main menu items outside the administration don't work too.

2. When adding/editing a venue, there is a blank row with "green plus" button for adding the new section to the venue. If you click on "save" button, this blank row is validated and it prevents you from editing/adding venue.

3. Add/Edit show - there are two "green plus" buttons, if you click on 2nd one (for Ticket Prices), the validation of Performance Date is triggered, that is wrong.

4. I can't find the way how to edit/add exact datetime of Performance, I can only select day.

5. The Section selector shows all existing sections, not only sections of selected venue.

6. Error message for description of event is wrong, it says: "An event's name must contain between 20 and 1000 characters", should be "An event's description..."

7. Add/Create show - performance dates are shifted by one day. E.g. if you set Oct 30, 2013, the Oct 29, 2013 is added as a date of performance

8. Newly created events can't be used for booking tickets, even if you create all required things (shows, performances, dates, ticket prices ...). In last step of booking procedure the error occurs: "Error! No entity found for query." I suspect that proper Section Allocation entity is not created. The same holds for newly created venues.

9. Show - Deletion of performance dates and Ticket Prices doesn't work. The items disappear, but after pressing "Save" button, they are back. Again (see 3.), the validation of performance date input field is triggered when clicking on red delete icon.

10. Ticket and Section Allocation - these two are good only for looking what is already there, the add, edit and search functionality is broken (maybe should not be there at all).

All the issues occur in both community and productized branches of Ticket Monster example.

Version-Release number of selected component (if applicable):

Ticket Monster example, version 2.1.0.ER2
Forge 1.0.5.Final

How reproducible:

Always