Login System where users can login and read safety forms and agree to them weekly.

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Login System where users can login and read safety forms and agree to them weekly.

Hello everyone,

I am new to this forum and unsure where to post my question about this so I figured the "general," category. Here is what I am trying to do:

1) Create a login interface/system where I am able to create multiple logins for different users for a company I work for.

2) Once logged in these employees are going to view weekly documents on informative or safety documents. These documents will have some type of timer to prevent speeding through them.

3) The employees will submit or confirm in some way that they have read the document and it will be recorded in a log per user that they have read the current document for the week.

4) Every couple of days or week we will have a new document for the employees to read.

5) The forms can be in formats of .doc, .pdf, .xlsx, etc., or just a regular plain text.

This system will be entirely simple and nothing fancy is required as long as the information is passed along everyone and we have a record of who has read it.

My questions is, what would be the best route or types of languages to involve in something like this? I am a little familiar with most of the languages but not a guru that is why I am here to get some help from the real gurus. Thank you!

If web application will be as simple as you have described, I do not think you will be limited on what language/framework/CMS to pick. My recommendation is to pick language you are most comfortable with. That way development will go faster and you will save time and with it, money. Perhaps you can even try picking Drupal CMS since it has a very nice built-in user system and it should not be too hard to extend it the way you want.

Hi Thanks for the response coding123. Ok so I happen to get my mysql and php to work with a very simple login page, now I would like to see if I can get some help with how to redirect to a "php/html" page only if login is successful. I do not want the page to be accessible without logging in

My preferred solution is to avoid the use of redirects. Instead create a file with all the necessary functionality to handle user authentication. Then you simply require() that file as the first thing you do on any page that requires the user be logged in. The include file includes the login form, and that form's action points to itself (action=""). The flow within the include file is something like:

You can test it out here:
iwirelessevolution.com/airwavesafety/login.php
username: username
password: 1234

My question is, how can I only allow access to the page if only the username and password is correct. Because right now I can launch the logged.php without logging in and I am able to access that page. I am really new to php coding so I need some help the most simplest way.

My goal of the project is to create a simple login to a "safety" database where couple days I can upload a new file to "read" and after the file is read, the person that is logged in can click some type of submit button to mark it as complete. Each user will have the same files but must login individually and mark as read meaning 1 user will only effect themselves when reading the document.

Structure of what I trying to do:

1) Login screen.
2) Login to "home page" for each user that can only be launched when their username & password submitted is valid.
3) They will login, be able to read a file either from a link or text and have an option of marking it "as read," then it will store it in some type of date category so they can go back to it.
4) This login system should be simple and solely only for reading a document, agreed they have read it and logout.
5) As an admin we should be able to keep a log of who has logged in and read which document.
6) I have access to mysql/sql server and godaddy windows hosting server iis7 asp.net 4.0 php version 5.3.

There are two basic approaches (that come to my mind right now, anyway):

1. Every page that is to have controlled access must be a PHP page, and must include code to check if the requester is logged in or not, and if not then take appropriate action (e.g. send them to a log page, or provide a link to the login page, etc.). See my previous reply for one approach of this type.

2. Store all controlled files outside of the web document root directory tree, create a single page that serves up the controlled pages (typically via include()) based on GET URL params -- possibly using web server URL rewriting to make the URLs more user-/SEO-friendly. If that sounds like a lot of gobbledy-gook to you, you're probably better off using the approach in #1.

"Please give us a simple answer, so that we don't have to think, because if we think, we might find answers that don't fit the way we want the world to be."
~ Terry Pratchett in Nation