5 replies to this topic

[djackson1001]

I have several errors that show up on my site. This has happened recently due to I believe an update on the server (providers) to PHP 5.3

[DunWeb]

@djackson1001


You duplicate post in the commercial support area requests additional information.  THIS post, will also require additional information.  However, if the error was caused by a PHP update, I would suggest you update your website to be PHP 5.3 compatible.




Chris

[germ]

djackson1001, on 11 June 2012 - 07:51 PM, said:

I have several errors that show up on my site. This has happened recently due to I believe an update on the server (providers) to PHP 5.3

All you have to do is force parameter 3 to be of the right "type" by putting (int) in front of it.

Edited by germ, 11 June 2012 - 08:29 PM.

[MrPhil]

germ, on 11 June 2012 - 08:28 PM, said:

All you have to do is force parameter 3 to be of the right "type" by putting (int) in front of it.

That's risky. The complaint is that the parameter is not a well-formed number. It doesn't matter if a well-formed number is in the form of a string -- PHP should convert it to an integer. It sounds like there is some other garbage in there. (int) may simply hide the problem by forcing non-numeric text to a 0. It would be better to find the source of the invalid data and fix it (upstream).

[germ]

MrPhil, on 14 June 2012 - 03:31 PM, said:

That's risky. The complaint is that the parameter is not a well-formed number. It doesn't matter if a well-formed number is in the form of a string -- PHP should convert it to an integer. It sounds like there is some other garbage in there. (int) may simply hide the problem by forcing non-numeric text to a 0. It would be better to find the source of the invalid data and fix it (upstream).

Probably not. I can't say I've ever seen a case where doing this would be "risky", personally.

PHP does a pretty good job converting strings to numbers and vice versa when it needs to most of the time.

Other times it requires a little help.

But unless the OP bothers to come back and post the offending code we'll never know.

[EricK]

Thanks, Jim, applied your 'fix' to this code in a fork of osC.

   $p_desc = substr(strip_tags($product['products_description']), 0, (int)MAX_DESCR_1);

Cheers,
EricK