Please I need help creating a user login page where every user log into their separate profile page

U shld be jailed for asking such question. U didn't even point out the technology u implored, if it worked or not, please go and read wikipedia on how to ask questions,or this thread be rather closed.its meaningless

I Salute all the gurus in the house, I am new to CMS, and I believe forums like this are created to assist all levels of knowledge. Explaining my question: Using Dreamweaver (PHP)+ WAMP, What I have done before is create a general user page where everyone who logs in access the same information, Now I want to create a dynamic site for a school where everyone logs into their own pages.

Am no php programmer,but in java ee 5/6 which relates to other server programming u need to know bout sessionscope and stateful ejbs,a sessionscope maintains a conversational state in a managed bean while a stateful ejb maintains a conversational state in an enterprise javabean.this means the resources are available throughout the session. 1st u need to have an entity ,with a username and password,who logins in @a front end and is validated frm the managedbean or ejb,obtains a session or JSession Id, that is available till it is expired.sessionscope r also useful when a logged in user uses a shoppingcart item that is available through sessionpages.
D entity can also terminate session by invalidating the session,session Ids are wat cookies on a browser refer to a particular entity in an application. When u hv multi entities to login to view their different pages,its left for u to decide what they see when they login,since different entities exists within the same application,a web filter is required so a particular entity doesn't navigate to a page he is nt authorized to go to (a filter checks the state if a session is active or expired). Al the best on ur research

Nw to ansa ur questn. Everytn wil depend on d username used 2 login.u wil need 2 get all informatn for d profile usin d where clause wit d username. E.g in a user informatn table u cn use sql lyk select* from user_info where uname = $_post['uname'];
it wud b wise 2 make d username a primary key

Thanks a lot Hoodboi, Javadoctor for your help. I really appreciate it.

Adamu,

With a good knowledge of RDMS , u can assign usergroups to users and menu items to usergroups.

This would ensure seperation of access to ur application.

poster,
you did not state what will be there in the profile when the user logs in.

poster,
let me know i can help using php/mysql

hoodboi:
javanian dat is no way to talk 2 sum1,even if u own nairaland. D poor guy jst nids help nd i blive dt is wt dis forum is about nt condemin d guy or tlkn 2 him anyhw.

Nw to ansa ur questn. Everytn wil depend on d username used 2 login.u wil need 2 get all informatn for d profile usin d where clause wit d username. E.g in a user informatn table u cn use sql lyk select* from user_info where uname = $_post['uname'];
it wud b wise 2 make d username a primary key

It would be unwise to make d username a primary key, u cld simply to validate a user with a query,
Select from the user table where username =:username and password:word ,depending on ur query language ,if the query returns null,redirect the login page ,cheers

hoodboi: Nw to ansa ur questn. Everytn wil depend on d username used 2 login.u wil need 2 get all informatn for d profile usin d where clause wit d username. E.g in a user informatn table u cn use sql lyk select* from user_info where uname = $_post['uname'];
it wud b wise 2 make d username a primary key

you don't need to make d username d primary key. u could maintain an autoincremented dint column as the p.key.

but since a lot of your search will be based on the username column, you could put an index on the column to make for faster search.

Y i mentioned usn d username is cux he ctd always use it as a secondary key in oda tables. Since it wud b a unique identifier.usn an auto-increament wudnt b wise cus of d secondary key.d num cn vary in oda tbles.wel design nd programas choice

@ Op,

Check this link out I designed something similar last week and it helped a lot.

http://www.phpeasystep.com/phptu/6.html

javadoctor: Am no php programmer,but in java ee 5/6 which relates to other server programming u need to know bout sessionscope and stateful ejbs,a sessionscope maintains a conversational state in a managed bean while a stateful ejb maintains a conversational state in an enterprise javabean.this means the resources are available throughout the session. 1st u need to have an entity ,with a username and password,who logins in @a front end and is validated frm the managedbean or ejb,obtains a session or JSession Id, that is available till it is expired.sessionscope r also useful when a logged in user uses a shoppingcart item that is available through sessionpages.
D entity can also terminate session by invalidating the session,session Ids are wat cookies on a browser refer to a particular entity in an application. When u hv multi entities to login to view their different pages,its left for u to decide what they see when they login,since different entities exists within the same application,a web filter is required so a particular entity doesn't navigate to a page he is nt authorized to go to (a filter checks the state if a session is active or expired). Al the best on ur research

Jsp heads and their "show-off" skills.

Urine:

Jsp heads and their "show-off" skills.

lol.