session_start problems with FireFox on Mac

Jochem Maas wrote:

> you also mentioned you changed the code when trying to test it on another
> machine - don't do that, test one thing at a time.

I'm not the original poster, that wasn't me.

> anyway problem solved, preventative knowledge aquired, onto the next
> hurdle :-)

I'm having some trouble with a for() loop and echoing array results
to screen to see if I'm getting the data I'm after, I may post about
it later.

Ulex

Europus schreef:
> Jochem Maas wrote:
>
>> you also mentioned you changed the code when trying to test it on another
>> machine - don't do that, test one thing at a time.
>
> I'm not the original poster, that wasn't me.
>
>> anyway problem solved, preventative knowledge aquired, onto the next
>> hurdle :-)
>
> I'm having some trouble with a for() loop and echoing array results
> to screen to see if I'm getting the data I'm after, I may post about
> it later.

use var_dump() rather than echo.

>
> Ulex
>

At 3:50 PM +0100 1/13/08, Jochem Maas wrote:
>to avoid this in future never add the closing php bracket to the end of
>the php file (unless you explicitly want to output something after the
>code in question - which is almost never the case), it is not required.
>
>e.g.
>
>--------- >8 info.php ----------------
><?php
>
>phpinfo();
>--------- >8 info.php ----------------

It may be a religious argument, but I always close my scripts and I
know where the white space is.

Also, most of my code is used by other languages (i.e., html, js) so
a closing bracket is always required -- unless it's the last function
in a file, but I haven't checked to see if that works in all cases.
So, I just always close it correctly.

Cheers,

tedd
--
-------
http://sperling.com http://ancientstones.com http://earthstones.com