Skip to content

Latest commit

 

History

History
12 lines (11 loc) · 2.43 KB

README.md

File metadata and controls

12 lines (11 loc) · 2.43 KB

WDC Project

  • Please install necessary libraries for the project that are listed in the package.json
  • For Google Sign-Ins, since we do not have an actual domain registered, if you try to use the Google Login in a non-verified origin path (domain), it will not let you and come up as restricted. This is due to the recent change in Google which took place on May 30th. Please contact us for this so that we can authorize your doamin (for cs50) so the login works.
  • The google login authorization may be buggy on cs50 due to unknown reasons, clearing browser cache may help.
  • In addition, google related APIs may not be initialized properly (most likely due to scripts not running in the correct order, or running at all, or just cs50 compatability issues), pages may require a reload to properly load them.
  • DO NOT USE INCOGNITO FOR THE WEBSITE, COOKIES DO NOT WORK ON IT AND THE WEBSITE WILL NOT FUNCTION PROPERLY SINCE IT RELIES ON COOKIES.
  • Each time you log out of the website, a google tab will open. This is to ensure that if you were using a gmail account to link your calendar, then that linked gmail will be logged out. If you had a calendar linked, this tab will open and then close after signing out. If you did not have a calendar linked, the tab will open and stay opened unless you close it. This is again to ensure that the user's gmail account is safe and does not stay logged in in the background.
  • There are two default entries in the User Table with user_id = 0 and user_id = 1. user_id = 0 contains dummy information about anonymous user when he subscribes to an event; user_id = 1 is the master admin. Master admin can sign up other admins.
  • Credentials for the ADMIN account are: EMAIL: [email protected] PASSWORD : wdcproj123
  • The way our project works is that as a user submits their availability, we get all the existing submissions and delete them from the database. We then compare the existing availabilities with the new availabilities, we reinsert the intersecting availabilities and discard the rest. This way, users don't filter the database items every single time they open the event page and we don't store unnecessary data since an event should only be held in times when all attendees are available, we only filter once upon a submission. The first submission automatically passes the filtering
  • The Google Sign In might be buggy on your own npm server. We request that you kindly contact us so that we can give you the link to ours.