singh1114 / eventsrest Goto Github PK

Remove django-bootstrap3 as dependency and add it as a simply downloaded bootstrap file in the static folder.

There are some function based views. Convert them into the class based views.
Use this https://docs.djangoproject.com/en/1.11/topics/class-based-views/intro/#using-class-based-views

If the user is already logged in there is no point in sending him/her to the login and signup pages.

Remove the django-bootstrap3 package from the requirements.txt as it is not required anymore.

Correct the spelling mistakes:
Imformation Technology - Information Technology

The purpose of using models in overridingAuth app is fulfilled by the use of User groups. So, there is no real need of them now.

Navigation bar at /parti_index/ is not rendered properly in chromium browser.

• Override the accounts to get a type attribute in it.
• Create the base app.
• Get the first view for participant i.e. the signup view working.
• Get the login view working.
• Create all the templates for participants.

Participant list is visible to the admin. There is no need for doing that.

At the login page, if we are getting a get request with query string with values of next, the query set is not handled properly.

Write code to handle the next query set.

For the time being,
I am able to detect the following problem in the models:

• The EventApp has a model of Participants_List which contain, EventId and other items like participant_name and all.
• This thing must be transferred to the overridingAuth app.

Solution
A good solution is to divide the model into two parts for normalisation purpose. The eventApp will contain a model having two fields i.e. event_id and participant_id( which is the foreign key to the overridingAuth app's participant model) and an overridingAuth/participant model containing all the attributes of the participant.

We have not added the correct URL in the href of the add profile card. Change it to the relevant URL i.e. /add_profile/