I never spend so much time with any package thus far on trying to get
it to work from the default build. I also trying to contact sf
support to see they can provide any help on this.
I download the nightly build on both sf and my pc to do a side by side
test in the effort to track down the problem. I set the debug to 3.
Again, I download the nightly build several times as you suggested and
you seem to think that the debug is 0 but that is the first thing I
did every time I download a new build and set the debug to 3.
I check the tmp for any log and the only thing that I see are what I
show here already other are cache file which is no value here. I
don't know where they put the apache log and I don't know whether I
will have access to it but that will be the next thing I will try to
look.
I do the debug line by line move up and down to get something to tell
me what is wrong and compare to my pc to see what are the potential
different and so far the only thing that I can tell is the name of the
object of "sessioncomponen" which is all small case where as on the pc
it is "SessionComponent"
Just to point out the only thing that I will get in the tmp dir are
when I put some debug code in the area that cause the "header
already.." otherwise there is nothing in the tmp dir. I also notice
there is no session file on sf whereas there are lot of session file
each refresh on my pc. That is the reason I think something to do
with the session or session component.
Well, this is very frustrating!
I might just drop this eventually if I can't get any further with
this.
Thanks for the help so far.
On Jul 6, 12:59 am, AD7six <[EMAIL PROTECTED]> wrote:
> On Jul 6, 4:19 am, "chanh.ong" <[EMAIL PROTECTED]> wrote:
>
> > I found this:
> > In 1.2, it gaves me sessioncomponent object name on sf.net:
>
> > $this->controller->{$component} =& new
> > $componentCn($param);
> > $loaded[$component] =&
> > $this->controller->{$component};
>
> > In 1.1, it gaves me SessionComponent object name on sf.net
>
> > $this->__controller->{$component} =& new
> > $componentCn($param);
> > $loaded[$component] =&
> > $this->__controller->{$component};
>
> > The class name is all lower case on sf in version 1.2 verse camel case
> > in 1.1 and that is the cause of my blank page.
>
> Pretty please stop.
>
> Only YOU can solve this problem, and the differences between php4 & 5
> are not the reason. None of the things that are the 'cause' in your
> messages are the reason you are getting a blank page. Don't you get an
> error log with sourceforge? What is in that (I don't want to know, I
> want YOU to read it)?
>
> I asked you about 5 days ago to download again, not touch anything and
> upload to your server (I didn't say download it to your computer, test
> it a bit and then upload it) and ensure that your DEBUG setting is
> greater than 0 (which it is by default). Did you do that? If you did,
> do it again please. if you didn't .... A blank page almost always
> means that DEBUG is 0 and either your tmp dir isn't writable (and it
> is full of cached config info for a different install) or the app code
> has a fundamental error in it.
>
> Cheers,
>
> AD
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
