Damn, that sucks.

On Sat, Mar 8, 2008 at 10:43 AM, Action <[EMAIL PROTECTED]> wrote:

>
> Also, their tech support gave me this response:
>
> " May I also point out that certain scripting engines that seek to
> control "everything" including GPC ($_GET,$_POST, etc) sometimes take
> and destroy the session variable. As a result you may wish to utilize
> the session_name(...) function and then ensuring the GPC control does
> not touch that variable-key in its cleaning."
>
> On Mar 8, 11:31 am, Action <[EMAIL PROTECTED]> wrote:
> > It turns outsessionswork fine on my host...justnotwithin Cake. If
> > I usesessions, either using cake's built-insessionsor from scratch,
> > within CakePHP, they are lost once I change/reload pages within my
> > site. My webhost is Medialayer.
> >
> > Any idea what could cause this?
> >
> > On Mar 7, 4:46 pm, Joel <[EMAIL PROTECTED]> wrote:
> >
> > > Sounds more like a server configuration issue than a Cake one.  What
> > > server is the host running?  Apache?
> >
> > > On Mar 7, 4:41 pm, Action <[EMAIL PROTECTED]> wrote:
> >
> > > > I recently switched web hosts and this problem arose:
> >
> > > > I have a login form. If the login info is correct, it creates a
> > > > session and redirects you to an admin page. The admin page checks if
> > > > the session is set and redirects you back to the login page if it is
> > > >not.
> >
> > > > This worked fine on my old host, but on my new host the session info
> > > > is lost once I redirect to the admin page after logging in (which
> > > > redirects you back to to the login page because the session is
> gone).
> >
> > > > How can I fix this?
> >
> > > > Thanks!
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to