[Resolved] Slow Cookies

Reformed

I am writing several cookies to disc and then displaying a page imediately after they are written that displays user information. My problem is that the initial page display shows no user info, but when I refresh the page, they are there. It's as if the cookies where being written very slowly. Here is the code in question:

$userView = unserialize($_SESSION['userView']);
            $_SESSION['userView'] = null;

        setcookie('windstorm', 'WINDSTORM_USER12f8jGlKQa7bi2LcX4zDi', LOGIN_EXP_TIME, "/");
        setcookie('userName', $userView->getFirstName(), LOGIN_EXP_TIME, "/");
        setcookie('secDesc', $userView->getSecDesc(), LOGIN_EXP_TIME, "/");
        setcookie('secLevel', $userView->getSecLevel(), LOGIN_EXP_TIME, "/");
        setcookie('userId', $userView->getId(), LOGIN_EXP_TIME, "/");

        $smarty = new Smarty();
        //add messages like these to a constants file (page titles etc)
        $smarty->assign('message', 'Welcome to Windstorm');
        $smarty->display('default.tpl.html');

Any have any suggestions?

bastien

RTFM

From the manual

Once the cookies have been set, they can be accessed on the next page load with the $COOKIE or $HTTP_COOKIE_VARS arrays. Note, autoglobals such as $COOKIE became available in PHP 4.1.0. $HTTP_COOKIE_VARS has existed since PHP 3. Cookie values also exist in $_REQUEST.

Reformed

The problem is that I need to access them on the page that this script is displaying (default.tpl.htm). Shouldn't the cookies be written before the $smarty->display() is called?

bastien

Cookies are written as part of the headers. What you can do is to place a js reload function that fires as the page loads to get the refresh.

Weedpacket

But you shouldn't really need to; you've already got the data you want to display on that page in hand - otherwise you wouldn't have been able to put them in the cookies.

Reformed

Well, I see what you mean, but I need that data to persist and it's use begins with that page. I found a workaround to the problem. Thanks for the suggestions.

Weedpacket

Originally posted by Reformed
Well, I see what you mean, but I need that data to persist and it's use begins with that page. I found a workaround to the problem. Thanks for the suggestions.

So what's this "workaround"?

Reformed

Well, since I use an MVC architecture, I just called my deafult action instead of calling the default template directly. That way the cookies are written while the classs redirects to the default action. Works pretty well.