PHP4 to PHP5

[Jeff]

I'm working on a server that is running PHP4.

I'd like to upgrade this so I can use the PHP5 code I have already.

What kind, if any, problems will I have with the existing PHP code base?

I see:

Local Master

magic_quotes_gp c On On
magic_quotes_ru ntime Off Off

I'm not sure what that means. I think that means that anything coming in
on $_REQUEST is backslashed and I'm thinking that probably won't play
well with PDO. If I turn that off what kind of failure could I see in
the existing code? Is that only a problem in that single quotes will be
backslashed in the data? Or can I have runtime crashes?

Jeff

[Twayne]

I'm working on a server that is running PHP4.

>
I'd like to upgrade this so I can use the PHP5 code I have already.

What kind, if any, problems will I have with the existing PHP code
base?
I see:

Local Master

magic_quotes_gp c On On
magic_quotes_ru ntime Off Off

I'm not sure what that means. I think that means that anything coming
in on $_REQUEST is backslashed and I'm thinking that probably won't
play well with PDO. If I turn that off what kind of failure could I
see in the existing code? Is that only a problem in that single
quotes will be backslashed in the data? Or can I have runtime crashes?

Jeff

We probably don't have similar code, but I made the switch and had zero
problems of any kind. The only problem I ran into was I discovered
filter_var in 5.2.5 and then discovered my ISP is only at 5.2.2, which
doesn't support it. So at least from my viewpoint, I'd say just make
sure you're at the same level your server provides. I just made the
switch on the server and ran a phpinfo() to get the full rev, then ran
one on my own system and compared the two. Past 5.2.2 there were some
pretty useful additions but I don't know them all by heart.

HTH

Twayne

[Jerry Stuckle]

Jeff wrote:

I'm working on a server that is running PHP4.

I'd like to upgrade this so I can use the PHP5 code I have already.

What kind, if any, problems will I have with the existing PHP code base?

I see:

Local Master

magic_quotes_gp c On On
magic_quotes_ru ntime Off Off

I'm not sure what that means. I think that means that anything coming in
on $_REQUEST is backslashed and I'm thinking that probably won't play
well with PDO. If I turn that off what kind of failure could I see in
the existing code? Is that only a problem in that single quotes will be
backslashed in the data? Or can I have runtime crashes?

Jeff

The change from php4 to php5 probably won't be too painful. Virtually
everything I've written for php4 runs fine on php5.

The magic_quotes_gp c may be another problem, however. You should have
it off (it will be removed in php6 because it never really worked). If
you've been depending on it being on, you'll have some code to change.

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

[Chuck Anderson]

Jeff wrote:

I'm working on a server that is running PHP4.

I'd like to upgrade this so I can use the PHP5 code I have already.

What kind, if any, problems will I have with the existing PHP code base?

I see:

Local Master

magic_quotes_gp c On On
magic_quotes_ru ntime Off Off

I'm not sure what that means. I think that means that anything coming in
on $_REQUEST is backslashed and I'm thinking that probably won't play
well with PDO. If I turn that off what kind of failure could I see in
the existing code? Is that only a problem in that single quotes will be
backslashed in the data? Or can I have runtime crashes?

Jeff

Just yesterday I ran into a problem with an old script I hadn't used in
a very long while. It accessed uploaded files via $HTTP_POST_FILE S,
which was still around in Php 4, but is gone in Php 5 (use $_FILES).

--
*************** **************
Chuck Anderson • Boulder, CO
http://www.CycleTourist.com
Nothing he's got he really needs
Twenty first century schizoid man.
*************** *************** *****

[Jerry Stuckle]

Chuck Anderson wrote:

Jeff wrote:

> I'm working on a server that is running PHP4.

I'd like to upgrade this so I can use the PHP5 code I have already.

What kind, if any, problems will I have with the existing PHP code
base?

I see:

Local Master

magic_quotes_g pc On On
magic_quotes_r untime Off Off

I'm not sure what that means. I think that means that anything coming
in on $_REQUEST is backslashed and I'm thinking that probably won't
play well with PDO. If I turn that off what kind of failure could I
see in the existing code? Is that only a problem in that single quotes
will be backslashed in the data? Or can I have runtime crashes?

Jeff

Just yesterday I ran into a problem with an old script I hadn't used in
a very long while. It accessed uploaded files via $HTTP_POST_FILE S,
which was still around in Php 4, but is gone in Php 5 (use $_FILES).

Yes, that could be. But even $HTTP_POST_FILE S is still available (but
deprecated). You enable it with register_long_a rrays=on in the php.ini
file.

BTW - $_FILES and the rest have been around since php 4.1. Any code
written since then should be using the new arrays. But I also suspect
your code was written before then :-)

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

[Curtis]

Jerry Stuckle wrote:

Jeff wrote:

> I'm working on a server that is running PHP4.

I'd like to upgrade this so I can use the PHP5 code I have already.

What kind, if any, problems will I have with the existing PHP code
base?

I see:

Local Master

magic_quotes_g pc On On
magic_quotes_r untime Off Off

I'm not sure what that means. I think that means that anything coming
in on $_REQUEST is backslashed and I'm thinking that probably won't
play well with PDO. If I turn that off what kind of failure could I
see in the existing code? Is that only a problem in that single quotes
will be backslashed in the data? Or can I have runtime crashes?

Jeff

The change from php4 to php5 probably won't be too painful. Virtually
everything I've written for php4 runs fine on php5.

The magic_quotes_gp c may be another problem, however. You should have
it off (it will be removed in php6 because it never really worked). If
you've been depending on it being on, you'll have some code to change.

This is the code I wrote, if I need to deal with the possibility of
magic_quotes_gp c being enabled. I don't know if this is the best, most
efficient approach, though:

<?php
if ( get_magic_quote s_gpc() ) {
$lambda = create_function ('&$str,$key',' $str=stripslash es($str);');
array_walk_recu rsive($_GET, $lambda);
array_walk_recu rsive($_POST, $lambda);
array_walk_recu rsive($_COOKIE, $lambda);
}
?>

--
Curtis (http://dyersweb.com)

[Jeff]

Curtis wrote:

Jerry Stuckle wrote:

>Jeff wrote:

>> I'm working on a server that is running PHP4.

I'd like to upgrade this so I can use the PHP5 code I have already.

What kind, if any, problems will I have with the existing PHP code
base?

I see:

Local Master

magic_quotes_ gpc On On
magic_quotes_ runtime Off Off

I'm not sure what that means. I think that means that anything coming
in on $_REQUEST is backslashed and I'm thinking that probably won't
play well with PDO. If I turn that off what kind of failure could I
see in the existing code? Is that only a problem in that single
quotes will be backslashed in the data? Or can I have runtime crashes?

Jeff

The change from php4 to php5 probably won't be too painful. Virtually
everything I've written for php4 runs fine on php5.

The magic_quotes_gp c may be another problem, however. You should have
it off (it will be removed in php6 because it never really worked).
If you've been depending on it being on, you'll have some code to change.

This is the code I wrote, if I need to deal with the possibility of
magic_quotes_gp c being enabled. I don't know if this is the best, most
efficient approach, though:

<?php
if ( get_magic_quote s_gpc() ) {
$lambda = create_function ('&$str,$key',' $str=stripslash es($str);');
array_walk_recu rsive($_GET, $lambda);
array_walk_recu rsive($_POST, $lambda);
array_walk_recu rsive($_COOKIE, $lambda);
}
?>

Thanks, I've added that to my php code snippets library.

I think it's more likely that I may need to turn on magic_quotes_gp c in
some existing code. No telling what may be there until someone
complains! I'm not particularly wanting to spider 60 domains and check
the code, there's enough I don't get paid for now!

I think PHP suffers from the same problem that ASP does. It's
perfectly easy for any idiot to write the most horrible unmaintainable crap!

Jeff

>
--
Curtis (http://dyersweb.com)

[sheldonlg]

Jeff wrote:

Curtis wrote:

>Jerry Stuckle wrote:

>>Jeff wrote:
I'm working on a server that is running PHP4.

I'd like to upgrade this so I can use the PHP5 code I have already.

What kind, if any, problems will I have with the existing PHP code
base?

I see:

Local Master

magic_quotes _gpc On On
magic_quotes _runtime Off Off

I'm not sure what that means. I think that means that anything
coming in on $_REQUEST is backslashed and I'm thinking that probably
won't play well with PDO. If I turn that off what kind of failure
could I see in the existing code? Is that only a problem in that
single quotes will be backslashed in the data? Or can I have runtime
crashes?

Jeff
The change from php4 to php5 probably won't be too painful.
Virtually everything I've written for php4 runs fine on php5.

The magic_quotes_gp c may be another problem, however. You should
have it off (it will be removed in php6 because it never really
worked). If you've been depending on it being on, you'll have some
code to change.

This is the code I wrote, if I need to deal with the possibility of
magic_quotes_g pc being enabled. I don't know if this is the best, most
efficient approach, though:

<?php
if ( get_magic_quote s_gpc() ) {
$lambda = create_function ('&$str,$key',' $str=stripslash es($str);');
array_walk_recu rsive($_GET, $lambda);
array_walk_recu rsive($_POST, $lambda);
array_walk_recu rsive($_COOKIE, $lambda);
}
?>

Thanks, I've added that to my php code snippets library.

I think it's more likely that I may need to turn on magic_quotes_gp c in
some existing code. No telling what may be there until someone
complains! I'm not particularly wanting to spider 60 domains and check
the code, there's enough I don't get paid for now!

I think PHP suffers from the same problem that ASP does. It's
perfectly easy for any idiot to write the most horrible unmaintainable
crap!

I have programmed in Fortran, PL/1, C, Java, Basic, Pascal, Cobol, PHP,
VB, DCL, sh, csh, etc. and there isn't a language that I have seen that
can prevent "any idiot to write the most horrible unmaintainable crap".

[Jeff]

sheldonlg wrote:

Jeff wrote:

>Curtis wrote:

>>Jerry Stuckle wrote:
Jeff wrote:
I'm working on a server that is running PHP4.
>
I'd like to upgrade this so I can use the PHP5 code I have already.
>
What kind, if any, problems will I have with the existing PHP
code base?
>
I see:
>
Local Master
>
magic_quote s_gpc On On
magic_quote s_runtime Off Off
>
I'm not sure what that means. I think that means that anything
coming in on $_REQUEST is backslashed and I'm thinking that
probably won't play well with PDO. If I turn that off what kind of
failure could I see in the existing code? Is that only a problem in
that single quotes will be backslashed in the data? Or can I have
runtime crashes?
>
Jeff
>

The change from php4 to php5 probably won't be too painful.
Virtually everything I've written for php4 runs fine on php5.

The magic_quotes_gp c may be another problem, however. You should
have it off (it will be removed in php6 because it never really
worked). If you've been depending on it being on, you'll have some
code to change.
This is the code I wrote, if I need to deal with the possibility of
magic_quotes_ gpc being enabled. I don't know if this is the best,
most efficient approach, though:

<?php
if ( get_magic_quote s_gpc() ) {
$lambda = create_function ('&$str,$key',' $str=stripslash es($str);');
array_walk_recu rsive($_GET, $lambda);
array_walk_recu rsive($_POST, $lambda);
array_walk_recu rsive($_COOKIE, $lambda);
}
?>

Thanks, I've added that to my php code snippets library.

I think it's more likely that I may need to turn on magic_quotes_gp c
in some existing code. No telling what may be there until someone
complains! I'm not particularly wanting to spider 60 domains and check
the code, there's enough I don't get paid for now!

I think PHP suffers from the same problem that ASP does. It's
perfectly easy for any idiot to write the most horrible unmaintainable
crap!

I have programmed in Fortran, PL/1, C, Java, Basic, Pascal, Cobol, PHP,
VB, DCL, sh, csh, etc. and there isn't a language that I have seen that
can prevent "any idiot to write the most horrible unmaintainable crap".

But *most* idiots wouldn't attempt to write C or Java or C++. Every
idiot thinks they can write ASP or PHP. They even have Complete Idiots
books for them. At least in PHP you can write well, I'm unconvinced that
is even possible in classic ASP.

Simple only encourages them. This is not a fault per se in the language.

Jeff

[Jerry Stuckle]

Jeff wrote:

sheldonlg wrote:

>Jeff wrote:

>>Curtis wrote:
Jerry Stuckle wrote:
Jeff wrote:
> I'm working on a server that is running PHP4.
>>
> I'd like to upgrade this so I can use the PHP5 code I have already.
>>
> What kind, if any, problems will I have with the existing PHP
>code base?
>>
> I see:
>>
> Local Master
>>
>magic_quot es_gpc On On
>magic_quot es_runtime Off Off
>>
>I'm not sure what that means. I think that means that anything
>coming in on $_REQUEST is backslashed and I'm thinking that
>probably won't play well with PDO. If I turn that off what kind
>of failure could I see in the existing code? Is that only a
>problem in that single quotes will be backslashed in the data? Or
>can I have runtime crashes?
>>
> Jeff
>>
>
The change from php4 to php5 probably won't be too painful.
Virtually everything I've written for php4 runs fine on php5.
>
The magic_quotes_gp c may be another problem, however. You should
have it off (it will be removed in php6 because it never really
worked). If you've been depending on it being on, you'll have some
code to change.
>

This is the code I wrote, if I need to deal with the possibility of
magic_quotes _gpc being enabled. I don't know if this is the best,
most efficient approach, though:

<?php
if ( get_magic_quote s_gpc() ) {
$lambda = create_function ('&$str,$key',' $str=stripslash es($str);');
array_walk_recu rsive($_GET, $lambda);
array_walk_recu rsive($_POST, $lambda);
array_walk_recu rsive($_COOKIE, $lambda);
}
?>

Thanks, I've added that to my php code snippets library.

I think it's more likely that I may need to turn on magic_quotes_gp c
in some existing code. No telling what may be there until someone
complains! I'm not particularly wanting to spider 60 domains and
check the code, there's enough I don't get paid for now!

I think PHP suffers from the same problem that ASP does. It's
perfectly easy for any idiot to write the most horrible
unmaintainabl e crap!

I have programmed in Fortran, PL/1, C, Java, Basic, Pascal, Cobol,
PHP, VB, DCL, sh, csh, etc. and there isn't a language that I have
seen that can prevent "any idiot to write the most horrible
unmaintainab le crap".

But *most* idiots wouldn't attempt to write C or Java or C++. Every
idiot thinks they can write ASP or PHP. They even have Complete Idiots
books for them. At least in PHP you can write well, I'm unconvinced that
is even possible in classic ASP.

Simple only encourages them. This is not a fault per se in the language.

Jeff

Jeff,

I agree. I've programmed in more languages than most - and some you've
probably never even heard of. In the years I've been programming and
teaching, I've seen some people try to write lousy code in other
languages.

For instance, they might try in C - but it isn't long before they have
real problems (i.e. bad pointers, insufficiently large arrays, etc.) and
give up. Even Java, with it's better handling of things, seems to deter
poor programmers.

But PHP and VBScript really do seem to attract poor programmers, and
even encourage them.

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===