Could you not write the new value to a SESSION variable and then pass it along that way?
(ie.
<?
session_start;
if (isset($_SESSION['oldEmail']))
{
// user submits form ... new email is written to a variable $newEmail
// do your update_user_meta etc updates to the DB ...
// I think session_register is deprecated now
// query the user table and get your newly updated email address for the ID of the user
// $resObj-> mysql_fetch_object the new email and register it in a temp session variable.
$_SESSION['newEmail'] = $resObj->user_meta_field_name;
$newEmail = $_SESSION['newEmail'];
$oldEmail = $_SESSION['oldEmail'];
$oldEmail = $newEmail;
}
?>
... carry on ...
Also sessions are specific to the web address in which you are submitting the data and the cookie ID needs to be set the same otherwise you are forced to carry the session over in the URL itself to the next the next location for evaluation: so if you are at http://yourplace.com and your post to http://www.youplace.com you will have problems. Keep the URL exact if it isnt that way already. (ie. <?php echo htmlentities($_SERVER['REQUEST_URI']); ?>)
This probably a little archaic, and not even certain it will work but just some initial thoughts.
I could be wrong, but I believe all WP user settings are cached to minimize DB hits. Part of the solution could involve flushing the cache and forcing it to reload, which is what reloading the page does. Or there’s probably a way to update specific cache data. Once the cache is correct, the currentuserinfo function will return current data.
Not a complete answer, but at least a likely fruitful avenue to follow.
I’m still working on a solution to my question, and it will likely have to include PHP sessions per billibones. WordPress’s internal cache is not persistent from page to page, and the only way to make it so is to use a plugin.
There are some issues with WordPress and PHP sessions that I’m working around, and once I’ve ironed out what works, I’ll post back. Currently I can set PHP session variables and output them, but regenerating a session with updated variables after submitting a form has been vexing. For some reason WordPress is either holding on to the header data, or I’m not regenerating the session in the right place in my code.
Hey Red, I’ve got one site that currently uses custom user meta, Im looking through that code to see what I did to navigate this situation and Ill post back … Hopefully we’ll find a resolution.
Cheers
I think I was heading down the wrong route with looking at a modified plugin of extra_user_details ( i thought maybe serializing the data/unserializing may have had something to do with it but i think I am offbase with that thinking.) … I did find a topic below that seems to deal with similar headache’s with sessions and WP … maybe it will help.
Hey I did find this out there though that might apply to your situation.
Adding a function to your template functions.php file:
function session_manager(){
if (!session_id()){
session_start();
}
$_SESSION['email'] = $_POST['email'];
}
Then calling it on the page with your form when the form is posted using add_action
include 'TEMPLATEPATH . /functions.php';
add_action('init', 'session_manager');
.. update user meta etc ... with user inputed data etc ...
This was from a post here in the forums from 2 years ago regarding a seperate issue with sessions.
@billibones – Thanks for the pointers.
I’ve been able to get this to work – let’s just say it’s good to pay attention to where the PHP session data is set and regenerated 😉 I had been overwriting my new session data with old variable values. Ahem.
For others who might be interested:
1) Out of the box WordPress doesn’t respond to PHP sessions without altering the config.php file or the functions.php file. This article was helpful to me: http://devondev.com/2012/02/03/using-the-php-session-in-wordpress/
2) Once I had set up functions to start PHP sessions and destroy them on login or logout, I was able to manipulate session variables via $_SESSION['key'] in either my header.php file — or in my particular case where I am processing form data and want the new values submitted by the user to update the session variables — at the top of my form after the $_POST data has been processed, but before WP’s header.php file is output. This way my header.php file picks up the new values of the PHP session variables.
3) This also gives you the ability to use any of the other PHP session functions such as session_regenerate_id().
