melcherst / htweb Goto Github PK

Navigation is currently embedded into the (admin) template. It's more efficient if it lives elsewhere and can be shared among both the normal and admin templates.

There should be a simple and small piece of UI in which the user can do the following:

• View all days of current week as session
• View # of people enrolled in session
• Action to (un)enroll in session for given day

This UI can be either on the dashboard as widget (maybe too small of an area to work with) or the My Sessions page.

Add an option to have repeatable/automatic products added once a receipt is created.

Advanced cms module featuring:

• post creation with wysiwyg editor
• media management

Introduce the ability to let others now you won't participate in a session

Remember me option doesn't seem to keep the session active on the device.

Users should be notified in the UI when action is required. There are a couple of cases that come to mind:

• A product is created in which the user participates
• Cook is in last day to change session information (and hasn't done so yet)
• A new receipt is created in which the user participates

There are probably plenty of other occasions..

Currently, products are static after creation. Maybe users should be allow to edit

• cost
• amount per member
• members

of a given product after creation.

PHP on external server runs in wrong timezone even though the system is configured correctly.
http://php.net/manual/en/function.date-default-timezone-set.php

Write the sum of the products in the product's cost field and the system will automatically add them together.

Since all information regarding points of all participants in a session is available it might be nice to predict which person should cook next.

If point division is unnecessary there should be a simple option to convert an existing session into a product

Create a framework that protects administration page for modules (based off of the default gate controller?)

ORMAuth currently used has no facilities for salting passwords. Introduce some sort of custom Auth that takes care of this

Bank account numbers are privacy sensitive information. They are no directly visible on the site and should be hidden by default (i.e. only be visible once it is needed). Some sort of 'click to show' mechanism would be nice.

On updating the user settings and changing the language the alert shown for updating the settings is loaded from the wrong (the not-updated) language file.

Currently, more than only contextual rights are controlled by the Auth_Context classes in the sessions and products module. There should be clear roles defining what a user can and cannot do.
These roles should mainly define general CRUD permissions and leave to more fine grained permissions work to Auth_Context.

Ex. case: delete product by another user.

• Check if user has role able to delete product
• Check context if this user can delete current product

Implement more presenters to reduce view code duplication.

There must be some system to deal with users leaving the system. The points of a leaving user must be spread over the remaining users etc.
Possibily some history record would be created to keep track of where all the points go.

(Image) Files served are currently just redirects to files in the Assets folder. This should be made more secure, with a controller actually checking if the requester has permission to view the file and only then serving the file.

Some new UI has been introduced on the index pages of sessions and products. This new 'sidenav-body' style should be further expanded to the receipts module and the session-view and product-view pages.

All database actions should happen in a single transaction during receipt creation as the current impl is prone to half-succeeded receipts etc.