gegmar / cluber Goto Github PK

• Log deletion of purchases by vendors
• Regular log of current sold tickets (Checksum / Trend)
• ...?

Allow configuration in an admin panel of long texts like ...

• Pdf-Ticket content
• terms and conditions
• data protection policy
• ...

Upgrade CSS/JS with current files

Select different seats/events for already paid/reserved purchases

Test all routes with dynamic data (HTTP level)

https://laravel.com/docs/5.8/http-tests

Es muss eine Möglichkeit geben, im Nachhinein die Abendkassa-Liste einzupflegen, um direkt aus dem Shop die Auswertung pro Tag erzeugen zu können.

If a customer undoes a purchase and has no other relations in the database but the role of a newsletter receiver, the delete statement fails because of foreign key constraint violations. This case has to be addressed, but has no higher impact on the shop (because only the user won't get deleted).

Get a report for a single event (also in the past)

• Add date to event names
• "Tagesabrechnung" for each event

Add an mail client to check for not delivered mails to customers.

Follow the upgrade instructions on https://laravel.com/docs/5.8/upgrade in order to upgrade the framework version to the most current one.

https://www.heise.de/ct/ausgabe/2014-26-Social-Media-Buttons-datenschutzkonform-nutzen-2463330.html

Feature-Flag/Setting for displaying remaining tickets

Currently it is optimized for frei.wild needs. Refactoring required

if a user goes back to their ticket selection, the price calc js does not work

implement a setlocale-mechanism for translated datetimes

use a simpler pdf-lib for ticket generation

Use the https://laravel.com/docs/7.x/eloquent-relationships#defining-custom-intermediate-table-models to add an order to every category attached to a price list

Implement localized eventnames

implement seatmaps to sell seats instead of amount of tickets

By checking the rows and columns of the seatmap scale the displayed map on the pdf in order to fit on one sheet.

• Configure for retailers the time until they can sell tickets for Events
• Configure for Events until when noone can sell tickets anymore

Extend price categories with a field telling whether or not a category can be purchased in ...

• the box office
• the presales phase

Create option to set prefered color set for css

Add configuration on how events shall be grouped:

• by date (-> LiterarturFestival)
• by project (-> Theatres)

• Customizable Texts
• A4? --> Format würde passen
• Text: It is allowed to bring the tickets on mobile devices --> Also as hint at the download page
• Add Purchase-ID
• Adjust Text-Size to length of texts

Configure Project to use npm for dependency Management of js-setup

Use https://github.com/PHPOffice/PhpSpreadsheet for creating Stats, Reports and Daily final Reports. This is much easier to maintain by utilizing templates.

https://github.com/PHPOffice/PhpSpreadsheet is not good for generating pdfs. This must still be done with the current HTML2PDF-Lib

Summary of ...

• Number of total sold tickets ("Wie viele Leute haben gekauft?")
• Where did they get their tickets? (Klarna|PayPal|Shop*|FreeTickets|Category)

@see: Report Helga

Ticketshop customers have no other Options to navigate to. So instead the full screen should be used for the shop.

Let the user decide how many events he wants to see instead of hard coding the next 5 upcoming events.

Implement the feature to let the user select whether or not he would like to have a smaller side menu

Select a single payment Provider that allows the following Minimum payment Methods:

• Sofort (Klarna) or EPS
• Any second Option

Currently prefered Option is Stripe.com

Enable authorized retailers to sell "free tickets"

Each instance of the shop shall be deployed with the following steps:

• (Re)Create QA-Environment with git clone/pull
• Duplicate prod-db to qa-db
• perform db migrations
• Run Operation Tests on qa
• (manually) Final Tests before prod-deployment
• backup prod-db
• backup prod-files
• set laravel into maintainence mode
• git pull
• run db migrations
• set laravel back to prod mode
  (Hopefully everything worked)

Integrate into a CI tool (Travis?)

implement administrative functions to manage events, projects, seatmaps, locations and more