How to redirect the users to their id specific setting pages after updating profile?

[polarexpress]

How to redirect the users to their id specific setting pages like

mysettings.php?id=1
mysettings.php?id=2
mysettings.php?id=3

after updating the profile or password there provided that the users are redirected to their id specific landing pages where they can navigate through the following pages / links dynamically as

myaccount.php?id=1
mysettings.php?id=1
admin.php?id=1 (Applicable for admin level only)
logout.php

myaccount.php?id=2
mysettings.php?id=2
admin.php?id=2 (Applicable for admin level only)
logout.php

myaccount.php?id=3
mysettings.php?id=3
admin.php?id=3 (Applicable for admin level only)
logout.php

and so on?

[Wombat76]

Just replace the numbers with $_SESSION['user_id'] and use the syntax (in PHP):

header ("Location: mysettings.php?id='".$_SESSION['user_id']."'");

Replace mysettings.php with myaccount.php, admin.php as required.

[Wombat76]

Or, if the user should click a link (in HTML):

<a href='mysettings.php?id="<?php echo $_SESSION['user_id']; ?>"'>LINK</a>

[weekendrockstar]

Well if they are logged in you shouldn't have to include user_id in the link because as long as they page they are going to makes use of the SESSION user_id it will get it from the session and wouldn't need to be passed along. You would only need to pass along an id if someone were viewing another person's page then you'd want to pass along the id. Or you'd want to pass along a user's idea if the page they're going to doesn't make use of the session information.

[polarexpress]

I guess none of you has understood my question.

The users can already navigate through pages dynamically linked with one another based on their ids stored in database during the login session when they are redirected to their landing / account page after successful login.

An example of such navigation of a user whose id is 1 is as following:

myaccount.php?id=1
mysettings.php?id=1
admin.php?id=1 (Applicable for admin level only)
logout.php

My question is that when the above user shall take attempt to update his profile or password using the profile update form or password update form at mysettings.php?id=1 page, how can he be redirected to same page or link itself (mysettings.php?id=1) after submitting the form?

Presently the user is redirected to mysettings.php from mysettings.php?id=1 after submitting the form at mysettings.php?id=1

How to associate or link the 'SAVE' and 'UPDATE' buttons available at mysettings.php?id=1 with mysettings.php?id=1 itself but not with mysettings.php during the update process.


Thank you,

[polarexpress]

Originally Posted by polarexpress

I guess none of you has understood my question.

The users can already navigate through pages dynamically linked with one another based on their ids stored in database during the login session when they are redirected to their landing / account page after successful login.

An example of such navigation of a user whose id is 1 is as following:

myaccount.php?id=1
mysettings.php?id=1
admin.php?id=1 (Applicable for admin level only)
logout.php

My question is that when the above user shall take attempt to update his profile or password using the profile update form or password update form at mysettings.php?id=1 page, how can he be redirected to same page or link itself (mysettings.php?id=1) after submitting the form?

Presently the user is redirected to mysettings.php from mysettings.php?id=1 after submitting the form at mysettings.php?id=1

How to associate or link the 'SAVE' and 'UPDATE' buttons available at mysettings.php?id=1 with mysettings.php?id=1 itself but not with mysettings.php during the update process.

Your guidelines are good for creating user id specific landing pages and dynamic URLs.

The solution is to leave the form action blank

Profile update form:
<form action="" method="post" name="myform" id="myform">

Password update form
<form name="pform" id="pform" method="post" action="">

Thank you,

[Wombat76]

Originally Posted by weekendrockstar

Well if they are logged in you shouldn't have to include user_id in the link because as long as they page they are going to makes use of the SESSION user_id it will get it from the session and wouldn't need to be passed along. You would only need to pass along an id if someone were viewing another person's page then you'd want to pass along the id. Or you'd want to pass along a user's idea if the page they're going to doesn't make use of the session information.

You are exactly right. My bad.

[polarexpress]

Originally Posted by Wombat76

You are exactly right. My bad.

Why login.php fails to accomplish the login session this way sometimes and redirect the users to their account pages (myaccount.php?id=1, myaccount.php?id=2 and so on.....)?

Aside from the existing code in myaccount.php do the developers have to put any other PHP code in it in order to redirect the users to their password protected account pages (myaccount.php?id=1, myaccount.php?id=2 and so on.....) based on their session id as mentioned in header of login.php?

Shall the users be redirected to their id specific pages definately based on the header syntax /header ('Location: myacaccount.php?id=' .$_SESSION['user_id']);/ of login.php only? If no, what shall make the log in process definately successful all times?

[Wombat76]

As weekendrockstar correctly said, when a user logs in their $_SESSION variables are set up which are accessible from every subsequent page in your website. Therefore it isn't necessary to pass the id number as a querystring of the header statement in login.php.

So, instead of using header ("Location: myaccount.php?id='" .$_SESSION['user_id']."'"); you can simply go back to the original header ('Location: myaccount.php');

Then, in myaccount.php, use

$id = $_SESSION['user_id'];

in order to get the user's id number. You can then use that variable $id to display the individual page for that user (which you must already be doing).

I'm not sure why login.php is failing to redirect correctly sometimes unless it's a timing issue, but if that is the problem, then the above change should solve it.

Sorry for the confusion and hope this explains it better.

[polarexpress]

Weekendrockstar is quite right but for convenience of some administrative tasks I would like to append the query string and it's corresponding values depending on the values of users' id stored in the database during registration process. The header syntex that uses user_id as session variable /header('Location: myaccount.php?id=' .$_SESSION['user_id']);/ must be good enough to serve the purpose as it is the primary key in the database table but surprisingly the log in session fails sometimes this way.

What could be the reason behind it?

Thank you,

[Wombat76]

I'm not sure why it should only work sometimes. When it fails, what is in the browser's address bar? It should read something like "...myaccount.php?id='1'".

[polarexpress]

I've figured out the problem finally.

The sessiona variable based header syntex

header('Location: myaccount.php?id=' .$_SESSION['user_id']);

in login.php is all right to redirect the users to the dynamic url based landing pages associated with their ids.

The problem occurs when the isset function (For checking the session variable) in myaccount.php is placed at any other place than the top of the page. The function fails to screen and check the variable sometimes when it is put at any other place than the top of the page.

In myaccount.php it is good to put the isset function just below the database connection and password protection syntexes to avoid any unexpected failure in log in session.

< ?php
include 'dbc.php';
page_protect(); ?>
<? php if (isset($_SESSION['user_id'])) { ?>

Thank you,