http://au2.php.net/session_write_close
The discussion here seems to indicate a PHP problem of some kind on
some systems.
or
Some missing stuff in cake to garbage collect for all situations?
or
Well my problem seems to point elsewhere.. __start in setFlash?
I encounter the problem with 1.2 +
debug(compact('message', 'layout', 'params'));
Array
(
[message] = foobar
[layout] = default
[params] = Array
(
)
)
That's the debug from the compact that goes into the write inside
setFlash.
-Ben
--~--~-~--~~~---~--~~
You received
Ok I've been through it from top to bottom on the writing side of
things, sessions, flash code etc.
Seems that there is something cleaning up the message value before it
gets to the session helper $session-flash();
Before the view (debug($_SESSION) at the top and no message). the
message is
Ok got it on my end.. Hopefully this can help some others.
Problem is in the example code for DAuth user login controller.
$this-DAuth-newSalt();
$this-Session-setFlash($error);
This resets the message all the time with a blank var ($error is blank
unless there has been one)
Mod to
I mean wouldn't
On Jan 15, 11:05 am, lordG [EMAIL PROTECTED] wrote:
Ok, yeah, the print_r would work as the session has not been started
yet.
However, there does appear to be a difference between when sessions
start for normal requests and ajax requests.
Ok, yeah, the print_r would work as the session has not been started
yet.
However, there does appear to be a difference between when sessions
start for normal requests and ajax requests.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
Ok, traced it down to the bare variable and these lines in the session
component:
00295 function __start(){
00296 if ($this-__started === false) {
00297 if ($this-__bare === 0) {
00298 if (!$this-id() parent::start()) {
00299
Does anyone have any further suggestions on this?
I cake 1.1 my ajax calls would work 100% with a session security set
to medium. With Cake 1.2 however they are no longer working.
It seems to have something to do with the $_SESSION array being
undefined when the response is received.
Shouldn't
ok... does anyone know why the following the the router are being
deprecated?
00503 /**
00504 * Deprecated
00505 *
00506 */
00507 $_this-connect('/bare/:controller/:action/*',
array('bare' = '1'));
00508
Hey Chris, yeah I had a similar problem before with 1.1 and did then
and now downscaled the security to medium.
What is the difference between the 3 levels though, other than the
timeout scale time?
Chris Hartjes wrote:
On Jan 13, 2008 6:24 PM, lordG [EMAIL PROTECTED] wrote:
Hi guys,
i'm having the same problem. (except minus the flash)
ugh...
On Jan 13, 2008 5:24 PM, lordG [EMAIL PROTECTED] wrote:
Hi guys,
I'm experiencing a problem with the redirects when I destroy the
session, set a flash message and then redirect.
When it gets to the redirect page, the flash no
On Jan 13, 2008 6:24 PM, lordG [EMAIL PROTECTED] wrote:
Hi guys,
I'm experiencing a problem with the redirects when I destroy the
session, set a flash message and then redirect.
When it gets to the redirect page, the flash no longer exists and the
session is clean of any custom session
12 matches
Mail list logo
