php-windows Digest 11 May 2001 07:10:54 -0000 Issue 591
Topics (messages 7471 through 7483):
PHP 4.0 and Payflow Pro
7471 by: Chris Mahaffey
Re: php-pws ques.
7472 by: Phil Driscoll
Re: anti-advocacy: Larry Seltzer, pcmag May'01 pub.
7473 by: Greg Brunet
7475 by: Greg Brunet
7476 by: Greg Brunet
7477 by: Cynic
7480 by: Greg Brunet
7482 by: Tim Uckun
Re: Need some HELP Please !
7474 by: DJ
7479 by: Vern DeHaven
UNC Paths with PHP4Win.de
7478 by: SHAWN
PHP/Apache on Win 2K "Internal Server Error"
7481 by: Nutchree P
Re: Need some dll's ! Please !
7483 by: Nold, Mark
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
Hello,
I am having a problem setting up PHP 4.0.5 to work
with Verisign's Payflow Pro. I have the Windows
Binary, PHP Source files and the Payflow Pro SDK. I
have seen in the language reference how to set up PHP
with the Payflow Pro extensions on a non-Windows box,
but I can't figure out how to do it for Windows. Do I
need to compile my own version of the PHP executable?
If so, how/what to do?
I do have PHP running perfectly without the Payflow
Pro extensions on a Windows 2000 Server with IIS 5.
Any help would br greatly aprreciated.
TIA,
Chris
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
I'm not sure what's going wrong in any of these situations - I think I've
missed the earlier messages, however this might help - it's some 'what to do
when it all goes wrong' notes which I'm about to add to the PHP Windows
installation instructions. Maybe they'll be useful in your situations maybe
not.
Cheers
- You have installed PHP, but when try to access a php script file via your
browser, you get a blank screen:
Do a 'view source' in the web browser and you will probably find that you
can see
the source code of your php script. This means that the web server did not
send the
script to php for interpretation. Something is wrong with the server
configuration -
double check the server configuration against the php installation
instructions.
- You have installed PHP, but when try to access a php script file via your
browser, you get a server 500 error:
Something went wrong when the server tried to run PHP. To get to see a
sensible error message, from the command line, change to the directory
containing php.exe and run
php.exe -i
If php has any problems running, then a suitable error message will be
displayed
which will give you a clue as to what needs to be done next.
If you get a screen full of html codes (the output of the phpinfo()
function) then
php is working ok, and your problem may be related to your server
configuration
which you should double check.
- You have installed PHP, but when try to access a php script file via your
browser, you get the error:
cgi error:
The specified CGI application misbehaved by not returning a complete set
of
HTTP headers. The headers it did return are:
This error message means that php failed to output anything at all.
From the command line hange to the directory containing php.exe. Run
php.exe -i
If php has any problems running, then a suitable error message will be
displayed
which will give you a clue as to what needs to be done next.
If you get a screen full of html codes (the output of the phpinfo()
function) then
php is working ok.
Once php is working at the command line, try accessing the php script via
the browser again.
If it still fails then it could be one of the following:
file permissions on your php script, php.exe, php4ts.dll, php.ini or any
php
extensions you are trying to load are such that the anonymous internet
user
ISUR_<machinename> cannot access them.
The script file does not exist (or possibly isn't where you think it is
relative to your web root directory). Note that for IIS you can trap this
error by ticking
the 'check file exists' box when setting up the script mappings in the
Internet Services
Manager. If a script file does not exist then the server will return a 404
error instead.
There is also the additional benefit that IIS will do any authentication
required for you
based on the NTLanMan permissions on your script file.
--
Phil Driscoll
Dial Solutions
+44 (0)113 294 5112
http://www.dialsolutions.com
http://www.dtonline.org
I suppose you could look at it that way, but actually, since VB isn't
case-sensitive, it wouldn't matter how I typed it as long as I spell it
right. So it's not like a spell checker correcting my spelling. Rather,
it's like a word processor applying the paragraph style for me instead of me
having to set my indents & tab stops manually each time.
Actually it does turn out to be both a productivity aid & verification tool.
It's faster because I don't have to shift case as I type & it verifies,
because if I see that it doesn't apply the proper case, I get immediate
feedback that I've mistyped the variable/function name. It would catch it
anyway when it compiles the code (just as C would catch an undefined
variable), but I don't have to wait till the compile step to correct it - I
can do it right there!
There are a number of things that MS does wrong, but this part at least
they've got very right.
-- Greg
"Bradley Miller" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Ok -- this too is not a flame, but just an opinion. I personally don't
> exactly like that much hand holding. It's like the "auto-correct"
features
> in MS products. Yea, it's great for productivity and that . . . but what
> reinforces the thought that you boo-boo'ed and didn't have to correct it?
> If I spell receive as "recieve" every time I type something . . . it's
> still not right in my mind . . . otherwise I wouldn't type it. When you
> don't have the crutch of the computer handy -- are you going to look like
a
> complete moron with all the "learned" typos that MS corrected for you?
> Tools should not instill bad practices and mask them for you. They are
> tools -- just that . . . they should enable you to work easier, but they
> shouldn't fix your work for you -- at least not automatically to where the
> conditioned response is "typos are good as long as the computer figures it
> out".
>
> -- Bradley Miller
Tom:
You've got a lot of good points through the whole message, so I won't quote
the whole thing.
First, I know that my "complaints" are probably going to be taken as an
ungrateful "us vs. them" attitude. Let me state up front that I think that
what all of the PHP developers/contributors have done is pretty awesome &
I'm thankful for their efforts. I want to make it clear that I am
appreciative of what they've done. That said, I would still respectfully
point out that the issues that have been raised can't just be given a pass &
should be given consideration.
Actually, I think that the installer works just fine & given that the ISAPI
module is not, in my opinion, ready for prime time, it is appropriate that
it installs the CGI module. Now one plus of PHP is that it's cross
platform. There is obviously a perceived advantage to developing API
specific versions such as the ISAPI module, and it's not unreasonable for
PCMag to test it - especially since one would expect better performance from
it than running in CGI mode. While I realize that PHP's heritage is not
Windows & the ISAPI module is unlikely to take priority, it's still
perfectly fair for PCMag's to ding them/us for ISAPI not running properly.
The problem of case sensitivity is not one of naming conventions and not
necessarily one of programming discipline. It is one of whether the tool
(PHP) helps the developer write clean code. I seriously doubt if there are
many (any?) developers out there who change the case of their
variables/functions from one instance to the next. If it does appear
differently, it would almost always be a typo. Without any warning that the
variable is undefined (the default way that PHP is installed), this can be a
key source of difficult to track errors. The two obvious ways to help
eliminate this kind of bug are a warning/error for undefined variables
(which is available within PHP - set error_reporting to 15 for those who
don't know about this yet), and switching to case insensitive
variables/functions.
To take advantage of case sensitivity to hack around something the language
is missing seems like a poor reason to implement it. If there is a
significant enough need to have multiple constructors, then that aspect of
the language should be addressed. Case sensitivity is not a nicety for
professional developers - it's just something that makes the
compiler/interpreter language parsing code easier to write. Making it
case-insensitive would help eliminate errors which I would think that all
developers, both professional & hobby, would welcome.
-- Greg
"Tom Mathews" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Seeing as how we're having a full fledged 'discussion' about this, I'm
going to
> throw my boot in from a programmers perspective.
> I know that historically php was Personal Home Page, implying that it was
> designed for use on personal web sites, not very sophisticated, no
security
> necesary ... just something that was free and easy to use for anyone
wanting to
> make their site a wee bit flasher.
> That was ten years ago (or therabouts) and like all things it has evolved
> massively away from the original concept. This evolution is thanks
entirely to
> the efforts of the unpaid developers that see something missing and write
a new
> module, or read lists like this and see what everyone else is having
problems -
> and write a new module to address this.
> The US and THEM attitude that is becoming prevalent in sectors of this
list is
> not really helpful for anyone - remember that PHP is Open Source - if you
want
> something changing, raise the issue on php.net, or better still do it
yourself.
> If you want a better installer for Windows 9x (if you must use that as a
> development environment) then write one.
> Of course there will be niggles, generally caused by different people
wanting
> different things. I guess that that is why the boys at Zend are starting
to
> produce more commercially oriented versions of it, and part of this is to
provide
> what the industry expect as well as home users. Things like case
sensitivity in
> variable names and function names have been prevalent since the early days
of all
> the UNIX variants for workstation or PC. If you have a problem with this
sort of
> thing, then you should probably take a wee step back from coding for a few
hours
> and start a naming convention that you are happy with, and while you're at
it (by
> the way Tim, this is not intended as a dig at you, so please don't take it
> personally!) just spend a little more time thinking about your programming
> discipline in general, keep everything consistent - if there's a team of
you
> working on the same app, then make sure that everyone knows the rules...
> I personally think that case sensitivity in names is very important. I
would use
> it in the absence of overloading, and the same again for classes where I
want
> different constructors to be employed. Be careful when you put in
complaints
> against this sort of thing that you think about the bigger picture - Open
Source
> will only survive if it competes equally with the commercial tools out
there. If
> you remove niceties that 'professional' developers expect, then they will
be
> forced to do the dastardly and buy MS type tools, and the benefits that
these
> guys provide to the Open Source community (like exercising all the
codebase a lot
> harder than homies that just use the basic functionaliy) will instead go
to MS!
>
> When I get time I'll put together a coherent article to defend php against
Larry
> Seltzer and his buddies,a nd I'll post it here first for review, but until
then
> that's more than enough waffle from me!
>
> Tom
>
>
>
----------------------------------------------------------------------------
----
> --
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
""Greg Brunet"" <[EMAIL PROTECTED]> wrote in message
9deuq7$j9k$[EMAIL PROTECTED]">news:9deuq7$j9k$[EMAIL PROTECTED]...
> Tom:
>
> You've got a lot of good points through the whole message, so I won't
quote
> the whole thing.
Oops - I did anyway - sorry 'bout that.
-- Greg
Hi Greg,
At 22:54 10.5. 2001, Greg Brunet wrote the following:
--------------------------------------------------------------
>Actually, I think that the installer works just fine & given that the ISAPI
This reminds me: me and Phil Driscoll have written new version of
the installer. Anyone on whose computer the installer failed is
invited to try the new version. instructions follow. (sorry for
the OT side note :)
>>How to do the test:
>>
>>Download the old version which I've put at
>>http://www.dialsolutions.com/phil/php/IISConfig.exe
>>
>>Then from the command line, run "IISConfig.exe <path to your php.exe> .php"
>>
>>so for example, on my system this would be:
>>
>>iisconfig.exe f:\php\php4\php.exe .php
>>
>>If one or other of the OCX controls is already registered on your machine
>>you should get a dialogue box showing a list of your IIS scriptmap nodes,
>>and you should cancel out of the dialogue box so it doesn't mess up your IIS
>>configuration.
>>
>>If however you get an error message to the effect that an OCX control is not
>>registered then good - you can help us!
>>
>>Run the IISConfig.exe that Cynic posted at
>>http://www.1st.cz/cynic/IISconfig.zip
>>with the same command line arguments.
>>
>>You should hopefully get a message box informing you that the control has
>>been registered, then the software should do it's stuff and display the
>>scriptmap nodes. Cancel out of the dbox and let us know it worked! NB the
>>software then unregisters the OCX again so that your system is left in the
>>same state as it was previously.
now, on to the topic.
>The problem of case sensitivity is not one of naming conventions and not
>necessarily one of programming discipline. It is one of whether the tool
>(PHP) helps the developer write clean code. I seriously doubt if there are
>many (any?) developers out there who change the case of their
>variables/functions from one instance to the next. If it does appear
>differently, it would almost always be a typo. Without any warning that the
>variable is undefined (the default way that PHP is installed), this can be a
>key source of difficult to track errors. The two obvious ways to help
>eliminate this kind of bug are a warning/error for undefined variables
>(which is available within PHP - set error_reporting to 15 for those who
>don't know about this yet), and switching to case insensitive
>variables/functions.
I'm ++1 on making PHP 100% case-sensitive. I just hate to see MySQL_Connect(),
MYSQL_Connect(), mySQL_DB_Query(), etc., in other people's source. It makes it
hard to read. It also makes the namespace much much smaller.
Failing to set your development environment for development isn't failure of
the language. It's a failure of the programmer. The facilities are there.
Of course, error_reporting E_ALL is a poor excuse for a debugger, but keep
in mind that you didn't have to pay a nickel for PHP. And the you have full
access to it's internals, so you can always write (or hire someone to do so)
an IDE that will catch your typos for you.
BTW, if you set error_reporting to 15 in PHP 4, you won't get almost any
error messages - numeric value of E_ALL is 2047.
>To take advantage of case sensitivity to hack around something the language
>is missing seems like a poor reason to implement it. If there is a
>significant enough need to have multiple constructors, then that aspect of
>the language should be addressed. Case sensitivity is not a nicety for
>professional developers - it's just something that makes the
>compiler/interpreter language parsing code easier to write.
Plus easier to read, and, believe or not, for some, it's easier to write.
>Making it
>case-insensitive would help eliminate errors which I would think that all
>developers, both professional & hobby, would welcome.
No. Certainly not. I guess there's a lot of people used to VB in php-windows@,
and I'm not subscribed to php-general@ anymore, so I don't know about that,
but everyone who raised their voice on this topic on php-dev@ or php-qa@ has
been for making function names case-sensitive.
>-- Greg
------end of quote------
cynic
Hi Cynic:
"Cynic" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> I'm ++1 on making PHP 100% case-sensitive. I just hate to see
MySQL_Connect(),
> MYSQL_Connect(), mySQL_DB_Query(), etc., in other people's source. It
makes it
> hard to read. It also makes the namespace much much smaller.
Actually, if they keep it case-insensitive, a tool to clean up the function
calls to match the function declaration might be useful. Of course
something like this couldn't be done if it's made case-sensitive. I would
agree that it cuts the namespace in half (much, much smaller sounds like
orders of magnitude). Still, the namespace is awfully big. Are you really
going to want to have variables x and X - or MySQL_Connect and
MySQL_connect? Can you honestly tell me that it will NOT be the cause of
errors down the road - maybe not by you, but by someone else who has to
maintain the code?
> Failing to set your development environment for development isn't failure
of
> the language. It's a failure of the programmer. The facilities are there.
> Of course, error_reporting E_ALL is a poor excuse for a debugger, but keep
> in mind that you didn't have to pay a nickel for PHP. And the you have
full
> access to it's internals, so you can always write (or hire someone to do
so)
> an IDE that will catch your typos for you.
>
> BTW, if you set error_reporting to 15 in PHP 4, you won't get almost any
> error messages - numeric value of E_ALL is 2047.
Thanks for pointing out the E_ALL constant - that is the right way to go.
Still, flagging undefined variables is only half the problem<g>.
> >To take advantage of case sensitivity to hack around something the
language
> >is missing seems like a poor reason to implement it. If there is a
> >significant enough need to have multiple constructors, then that aspect
of
> >the language should be addressed. Case sensitivity is not a nicety for
> >professional developers - it's just something that makes the
> >compiler/interpreter language parsing code easier to write.
>
> Plus easier to read, and, believe or not, for some, it's easier to write.
I think that there is a disconnect between the case-sensitive (CS) and
case-insensitive (CI)proponents. I, and I expect most other
case-insensitive advocates are not expecting or desiring to refer to the
same variable/function with different case usages. We just want it to be
treated the same in case it does get typed with a different case. I expect
that my naming conventions are similar to yours - there already exists in
the computer field some generally accepted practices that it makes sense to
follow. I also adhere to the case of pre-defined functions, constants, &
variables. Thus, I expect my code will look just like yours, so it will be
just as easy (or hard) to read or write it as yours. The only difference is
that I won't be able to have x & X refer to two different
variables/functions which is confusing & leads to bugs.
> >Making it
> >case-insensitive would help eliminate errors which I would think that all
> >developers, both professional & hobby, would welcome.
>
> No. Certainly not. I guess there's a lot of people used to VB in
php-windows@,
> and I'm not subscribed to php-general@ anymore, so I don't know about
that,
> but everyone who raised their voice on this topic on php-dev@ or php-qa@
has
> been for making function names case-sensitive.
I'm comparing it to VB only because many people are familiar with it. I've
used quite a few languages over the years, and have read & used different
coding styles & standards. The argument is not one based on VB familiarity,
but rather cross-language best practices (for the using programmers). I'd
like to hear why the folks on the other lists they want case-sensitive
functions & if the arguments are from a user perspective or a tool developer
one.
BTW: I checked the other lists you mentioned & saw your message from this
board. Thanks for letting the folks there know about some of our concerns.
-- Greg
>No. Certainly not. I guess there's a lot of people used to VB in php-windows@,
>and I'm not subscribed to php-general@ anymore, so I don't know about that,
>but everyone who raised their voice on this topic on php-dev@ or php-qa@ has
>been for making function names case-sensitive.
I guess I don't find that very surprising. The people on those lists are C
programmers who are very comfortable with a case sensitive language. The
typical user of PHP is most likely not a C programmer and in fact very
likely to be switching from Cold Fusion or ASP in the windows platform. If
you want to lure these people into your world it might be a good idea to at
least have an option to turn off this "feature".
Maybe you have point when you say it makes it hard to read when people
write MySQL_Connect(),
MYSQL_Connect(), mySQL_DB_Query(), but it will be a nightmare when
getLastWord($s) and GetLastWord($s) will actually be two different
functions which may perform two different things. Try debugging that!
----------------------------------------------
Tim Uckun
Mobile Intelligence Unit.
----------------------------------------------
"There are some who call me TIM?"
----------------------------------------------
I just finished installing PHP on a Win98 PC with Microsoft Personal Web
Server.
I'd downloaded the Windows PHP setup here: http://php.weblogs.com/ Be sure
to read the readme file.
Have you done this?
"Walter Schruefer" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hi everybody !
>
>
> We are trying to install PHP 4.0.5 and Xitami 2.5 on a win98
> and we donīt get PHP to work. Is anybody available to give
> us some ideas where to look first?
>
>
> Any help would be kindly appreciated.
>
>
>
> Regards
> Walter
>
> --
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
>
Network BlitzTHANK YOU times 1000! This installer uses 4.0.4, which seems
to work beautifully with PWS. I could not get 4.0.5 or 4.0.6 to work with
it.
OK now, what kind of functionality is mising? Hmm...
Another thousand thanks,
Vern DeHaven
"DJ" <[EMAIL PROTECTED]> wrote in message
9derdj$e07$[EMAIL PROTECTED]">news:9derdj$e07$[EMAIL PROTECTED]...
> I just finished installing PHP on a Win98 PC with Microsoft Personal Web
> Server.
>
> I'd downloaded the Windows PHP setup here: http://php.weblogs.com/ Be
sure
> to read the readme file.
>
> Have you done this?
>
>
> "Walter Schruefer" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > Hi everybody !
> >
> >
> > We are trying to install PHP 4.0.5 and Xitami 2.5 on a win98
> > and we donīt get PHP to work. Is anybody available to give
> > us some ideas where to look first?
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Does anyone know if the fix for the UNC path problem was included in the
current build from php4win.de?
Thanks in Advance!
Shawn Sellars
I followed the installation steps.
1) Configured the httpd.conf
# for the apache module
LoadModule php4_module c:/php/sapi/php4apache.dll
AddType application/x-httpd-php .php4
#for the cgi binary (you can use that one compiled with force cgi
redirect too)
ScriptAlias /php4/ "C:/php/"
Action application/x-httpd-php4 "/php4/php.exe"
AddType application/x-httpd-php4 .php
2. Unzip the Package to c:\php, now move php4ts.dll to the
windows/system(32) directory, overwritte any older file!
3. Copy the php.ini-dist to your sysroot (directory where you installed
windows), rename it to php.ini, and
edit the php.ini to fit your needs.
However, I keep getting "Internal Server Error" and "The server
encountered an internal error or misconfiguration and was unable to
complete your request."
Please help. I am stuck here.
Whatever suggestions will be very helpful.
Pom
----------------------------------------------------------------------------
-----------------
Disclaimer: The information contained in this email is intended only for the
use of the person(s) to whom it is addressed and may be confidential or
contain legally privileged information. If you are not the intended
recipient you are hereby notified that any perusal, use, distribution,
copying or disclosure is strictly prohibited. If you have received this
email in error please immediately advise us by return email at
[EMAIL PROTECTED] and delete the email document without making a
copy.
----------------------------------------------------------------------------
-----------------
Have you tried
http://php4win32.sourceforge.net/releases/php-4.0.6-dev-20010504.exe
I havent tried this particular install but these guys (www.php4win.de)
create an extensive range of Windows PHP binaries.
BTW: You cant just pick up the .dlls and run with your version of PHP as im
sure they are sensitive to which point version you are using ie: 4.0.5 dll's
will not work with 4.0.4 (AFAIK)
mn
Mark Nold
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Senior Consultant
Change is inevitable, except from vending machines.
-----Original Message-----
From: Cornel CRISAN [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 10, 2001 10:45 PM
To: [EMAIL PROTECTED]
Subject: Need some dll's ! Please !
Hi there !
I'm using WIN98+PHP4.01+Apache1.3.19 and I need some dll files...for
some function that I'm using for graphics and snmp !
php_gd.dll
php_snmp.dll
CAN SOMEBODY SEND THEM TO ME PLEASE ! There are only two link where I cand
find these files and both are DOWN !
Thanx !
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
