quantumlicht / php-wine Goto Github PK

put all input fields to lower cap. this way when someone searches we wont have to deal with capitalization.

Add form validation and trigger errors.

Création d'une table qui contient toutes les informations pertinentes lors de la création d'une fiche.

On y met la couleur des vins, les mois de l'année et on fait un lien avec tout les producteurs, les cepages, les appelation et les régions qui sont générées par les utilisateurs.

This waay we dont have to go through each files looking for links and replace them.

Ajouter tout les encepagement qui se trouve dans le cahier des vins.

When a field is deemed invalid, add the bootstrap class that will toggle it as an error.

i.e. maybe try netbeans.

Make sure that the field that do not come from a dropdown are sanitized. i.e :

• prix is numeric
• alcool is numeric
• nom is html escaped and of a maximum length
  -same for all text field.
  make sure wine color has been selected.

anything else that can be thought of.

This way we can pass which database we want to connect to.

make an sql dump and save it to ubuntu one

On met les données nécessaires à la génération du formulaire pour la création d'une fiche dans une table de la DB afin que les infos soient accessibles pour d'autres pages également.

convert type for
alcool ,prix

limit number of selected encepagement
make sure all text field don't contain numbers

It shows the first option by default. We need to add an field that will be empty , thus detecting if the field has been selected or not.

Maybe use an already existing class that will sanitize input and make sure that there is no abusive behavior in the inputs.

Add a row in the user table that defines if the user is admin or not.
The admin login page should only be accessible if you have admin priviledge, and you still need to provide your credentials.

Try to condense the code so that it's more compact. It seems like it will be painful to maintain because it is a huge chunk of html code. Its certainly possible to port some of it to Jquery.

Maybe this would also contribute to remove load off the server.

When we navigate to a page, we should the tab changing state.

Try to toggle 'couleur du vin' properly to ensure that we can only select one value( radio button ) and also make sure that we will be able to retrieve the selected value in the form to inject into the DB.

As of now, we call the controller directly which exposes the directory structure

Ça prend un moyen pour afficher les couleurs selon que l'on sélectionne le bouton rouge ou le bouton blanc.

La solution simple serait d'ajouter le contenu des deux listes, mais d'afficher seulement une selon le bouton qui est sélectionné.

we should change trigger to focus or somethinng else appropriate

These tags should show up as they are added and could be removed with a small x icon at the top-right corner. Just like when you add tags in Jira

It is not currently added into the database

Enable users to populate tags list.
However there should be an interface in the admin section to manually remove bad tags, and also have a mechanism to prevent users from posting abusive tags:

tags should limit to 1 word
no numbers
escape any html tags
limit number of characters.

Add an admin tool to list the content of the tables.

Have a tool to add html code inside a container on the front page that will also be stored in the database

1 table pour le rouge et une table pour le blanc.

No way for the user to know if the request succeeded or not.

Add type ahead for :

1. Region
2. Producteur
3. Appelation

Will populate arrays with info from database harvested from previous submitted wine forms.

Modifier l'emplacement du contenu pour que la couleurs des vins( blanc et rouge) soit stocké dans la base de données et même chose pour les mois de l'année. On y accède ensuite par le modèle. Ce sera plus versatile, car il y aura d'autre page qui vont accéder à cette information aussi.

Add a git ignore to prevent committing swap files

It should link to all the models that actually create the tables.

We would also need redirect to the admin page upon creation with the status wether it was created or not.

Also add a button to redirect to the main section
Of course this section should be protected.

Ui des not show properly for small screens. Add fluid containers on all divs

Participez et dégustation

Try to make sure that the validation toolbox is more generic and can be reused for many different form inputs.

Try to find a library that does general form validation. i.e a first pass of sanitation that escapes html properly . Then, we can focus on parsing content to check if it matches an expected content template.

We shouldnt need it anymore since we now use a root controller that already connect to the database