It could be that you have local error reporting set to none. It could also
be that you're using full paths when referencing files which then breaks
when moving files to a new server. Basically, there's a lot of
possibilities and I'm not going to have much luck helping unless you include
error messages. My guess is that resolving a few errors will address a core
problem and everything will start working.
-Ed
> That's what I thought. But the differences are glaring. Seems like none of
> the
> code wants to work. Navigation is a nightmare: header("location:...");
> usually brings an error message: function so and so -- include("xxx.php");
> has already been declared -- cannot redeclare (yet locally - absolutely no
> problem!) ??
>
> Oh, what a nightmare. I can handle parsing errors, and general messups --
> but
> when the whole site works without a glitch locally . . . .
>
> Also, mysql complains bitterly about a non-existent user (it's already an
> open
> and persistent connection, has given data previously -- go figure) -- it's
> unbelievable! And I have an existing site, developed using almost the same
> code + 340++ files working seamlessly.
>
> The libraries appear to be the same, however, I did notice a reference to
> /usr/lib/pear. include paths point correctly, and I faithfully use <?php
> ....
> ?>.
>
> Sigh -- what a mess!
>
> Andre
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
