php login behaviour shows errors

[ChrisHe]

Is there a problem with the Dreamweaver standard php behaviours? In particular
the user login scripts?

e.g. I have tried with both the "Newland Tours" demo (php_users), and just
inserting the login php "behaviour" into my own pages.

With php and MySQL error logging ON, i get the following:
"Cannot modify header information, headers already sent"
and
"1 result set not freed..."

altho the script does seem to work.

Is the standard php code from Dreamweaver just not very good - it certainly
seems to be complex to me, as a newbie, so I can't see what is wrong, but
perhaps some more experienced person knows about this?
And are the other behaviours just as flaky? (assuming it's not my fault
somehow!)
I'm a newbie to this, but feeling very cautious about Dreamweaver now..
Thanks
Chris

P.S. I already picked up the following "error" - should use $_SESSION and not
$_GLOBALS (which is deprecated by php)
I'm using php 4.3.10, DWMX2004, Mysql 4.0.20d

[Felix1]

Probably you have a white space after the connection string or some other
interruption. Remove it. <?php require_once(...............); ?> <-- just
here Is nothing wrong with the DW's Login User. Felix

[David Powers]

ChrisHe wrote:

> Is there a problem with the Dreamweaver standard php behaviours? In particular
> the user login scripts?

The PHP User Authentication scripts in Dreamweaver MX 2004 use
deprecated code. I have written a detailed analysis (together with the
solution) here:

[url]http://friendsofed.infopop.net/2/OpenTopic?a=tpc&s=989094322&f=8033053165&m=3241024 21&r=324102421#324102421[/url]

> With php and MySQL error logging ON, i get the following:
> "Cannot modify header information, headers already sent"
> and
> "1 result set not freed..."

"Headers already sent" is a common problem for beginners. It means that
there is whitespace outside the PHP tags before the script gets to
session_start(). Felix has shown you one possible place this may be. The
other very important place to look is in your Connections file. There
must be no extra lines after the closing ?> tag on the page. Switch on
line numbering in Code view. If you can see any numbers after the final
tag, that's where your problem lies. Put your cursor as far down the
page that it will go, and use backspace to delete all the whitespace
right up to the closing ?>.

> Is the standard php code from Dreamweaver just not very good - it certainly
> seems to be complex to me, as a newbie, so I can't see what is wrong, but
> perhaps some more experienced person knows about this?

A lot of experienced people don't like the PHP code in Dreamweaver. It's
not so much that it's bad, but that it is very verbose. The reason is
because the Macromedia development team has had to second-guess just
about everything that someone is likely to use or enter in an online
form. It's catch-all code, rather than the lean, clean code that you
should eventually start writing when you get more experienced and don't
need to rely on DW for everything.

One thing the DW code is very good for is rapid development of a
prototype. You can rustle up a quick (albeit simple) database-driven
site with DW in an hour or so (once you're reasonably proficient). That
will show you or a client the basic outline of what a site will look
like. Then you get down to the detailed coding, most of which has to be
done by hand.

> P.S. I already picked up the following "error" - should use $_SESSION and not
> $_GLOBALS (which is deprecated by php)

Yes, that's the deprecated code that I mentioned at the beginning. In a
lot of recent setups, it now fails completely. It's a bug, but one that
MM has not yet corrected.

--
David Powers
Author, "Foundation PHP 5 for Flash" (friends of ED)
Co-author "PHP Web Development with DW MX 2004" (Apress)
[url]http://computerbookshelf.com[/url]