gubrus50 / baketoom Goto Github PK

User should be able to change their password safely, in this case, their email will have to be used. When the submit button is pressed, a form is sent to the user email. Once confirmed and details have been submitted, the change will take place, and user will be notified via email and our message container (bell).

The current website uses polish as a standard language, so it's obvious that terms must be clear for the polish users. Translate terms_and_service.html and privacy_and_policy.html (templates) to polish.

Browsers will not promote the website under the domain "www.baketoom.com" because it lacks an up to date wildcard certificate, which in result makes the domain look untrustworthy to the visitors.

This issue can be fixed in 3 ways. Find the reason why it's not appearing and fix it. If it's impossible, use a command "recipe.country/nationality.flag" from already installed plugin -> https://github.com/SmileyChris/django-countries. The last solution would be to replace the image with the full name of the country.

Create a feature where the user can set a license for their recipe.
Once the user tries to create a recipe, in the form, a custom-license will be set as default with empty content data. I would suggest to use a drop-down option followed by a textarea with license content. If the user does not appreciate the available recipes, they can always edit the textarea.

BACK-END:

• recipe model must contain a text field to store the license.
• recipe-form template must register the license field.
• recipe_form.js must contain a function that will load the selected license.

FRONT-END:

• recipe-detail template must contain the licence container. (Display it after the method container).
• recipe-form template must display a drop-down menu of available licenses.
• recipe-form template must display textarea with CUSTOM-LICENSE set as default content (empty).

Create a template form where non-registered user can report a recipe. To submit the report, they must include their contact details such as phone number or email to prevent spam and prove identity, also they must supply as many details as possible. If they claim for their ownership, they must supply solid evidence, else we will not take recipe down. We will also inform the recipe host of the individual.

Consider the following:

• reported recipe brakes our terms and privacy.
• reported recipe claims MY recipe (EU article 13 - copyright).
• reported recipe distributes MY recipe without permission / appropriate license.

An additional change that may be required - User must choose whether or not they are the author of a published recipe. Else, they will have to provide us with a license of the recipe in the recipe_form.html template, in result, their status of the recipe will change from "author:" to the "publisher:".

Create a bell icon / message option in the navigation bar so we can have an easy way to respond to our users.

The current images used are just a template. To protect the project from copy-strike law (https://copystrike.net/article-13-copyright/), I will have to create my own or buy new images for default display for profile and recipe picture.

Create an introduction template which mentions our values, to show newcommers who we are,
and what is our website all about.

Recently, I noticed that every occurrence of a hyperlink at the bottom of the mentioned template is not initialized with the required URL.

Our website should be hosted on Heroku.com, under the domain name "baketoom.com".

Create and set-up appropriately the following emails for our website:
[email protected]
[email protected]

12/6/2020 you can create google DOMAIN and link it to our team Gmail account.

Plain view located at URL: "domain/recipe/plain/<recipe_id>/" is used to download and print recipes. This page lacks 'responsiveness', which is a problem when you're trying to read a download of a recipe on a small device like android.

Recipe_detail template receives all Categories. This is insufficient because every recipe requires their categories ONLY.

reCAPTCHA integrated in forms.py has no issues. However, some templates do not use forms.py. For example, templates: login.html, BUT! I haven't checked for all templates. I assume that the register.html form may also fail despite the reCAPTCHA being rendered from forms.py, but I'm not certain.

I tried integrating reCAPTCHA manually in these templates by providing the necessary data. I have even created exclusively context_processors.py for passing required RECAPTCHA keys. Unfortunately, reCAPTCHA is ignored when submitting these templates form. I don't know how to fix that, so I will leave it as an open issue.

When modifying existing recipe categories, the user may experience random bugs caused by undefined variables in RecipeUpdateView(). I have no idea why this occurs.

The variables that are not getting defined are usually those which are trying to receive the data from the database. I have tested the application locally using Django with Postgresql and everything seem to work, I assume that this may have to do something with the DNS response.

Since currently, I don't have a great understanding of Heroku, I will have to leave this issue for the time being, and keep the registration private until the right time comes.

Our hosting platform has removed database. Currently, we have managed to save past recipes images using different PaaS, but their content is gone. Hence, we need to create new recipes and for the future, create a monthly backup of the integrated database service.

User should be able to search a recipe by published / edit date, special approval certificate and by recipe origin e.g. country.