PP 4.8c incompatible with PHP 4.3.6

[rbl]

I've reported on another thread a problem with function mysql_num_rows() that popped up since my host upgraded their PHP to 4.3.6

Now, I'm getting reports from users that are getting the same error in several other places where this function is used, like listing all photos in any category.

These are the errors when I try to list all photos on my site:
Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /path/to/photopost/showgallery.php on line 409

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /path/to/photopost/showgallery.php on line 416
note paths edited for the sake of reading

I need a fix for these urgent!

Thanks!
Ricardo

[Chuck S]

Well mysql_num_rows is not incompatible with 4.3.6 at least thats what php.net says

http://www.php.net/manual/en/functio...l-num-rows.php

That is at least what they say. I dont have 4.3.6 to test on.

[rbl]

Well.. maybe not incompatible, pardon my english =)

I can't had count(*) to it because this is the main function that calls the photos from the database in showgallery.php and not a simple function to count the number of rows.

[Chuck S]

What I am saying is given PHP.net documentation mysql_num_rows and * are still valid thats all I am saying.

[rbl]

I'm not questioning that!
But that doesn't change the fact that I'm getting these errors all over the place where mysql_num_rows is used.

[rbl]

what about replacing mysql_num_rows by mysql_fetch_array?

[Chuck S]

well I just installed bigapache on my home machine with includes php 4.36 and mysql 4.0.18 and everything is fine with mysql_num_rows and Photopost.

Let us check into this more. I will talk with Michael some about this when he gets back in town. Everything I am reading in the php docs etc says no problem with mysql_num_rows and it works fine for me so dont know yet whether its just server specific or whether they updated mysql as well when they updated php and messed something up.

[rbl]

I appreciate it!
Let me know if you need access to a phpinfo page.

[DerekT]

I'm running 4.3.6 and have no problems.

[Chuck S]

Yep there is not a problem with php 4.3.6 and mysql_num_rows. I have installed 4.3.6 and also went back and checked phpinfo pages on some of the last installs I have done and many are running 4.3.6 and some even 4.3.7 with no problems

Has to be an isolated incident where RBL's host messed something up when they updated their php/mysql

rbl you can PM me a test account and url etc and I will take a look

[rbl]

Sorry for the delay on this one but it was a very nasty bug to solve.
After a few tries, we have isolated this to a kernel problem. Took a lot of time because the logs were clean: no clues, no traces... nothing.

The problem was constant lost connections to the mysql server. These caused the mysql_num_rows errors in every file that used them. I've kept my changes for the times mysql_num_rows was used to count rows. The COUNT(*) function is better.

As soon as I know anything else about this particular kernel issue, I'll post here. Maybe it would be helpfull for someone.

Anyway, my apologies and thanks to everyone that lost time with this issue but unfortunately this was beyhond my control =(

Ricardo

PS: almost forgot! PP is running on php 4.3.7 with no problem whatsoever =)

[Chuck S]

RBL

Understand completely. Server issues and misconfigurations etc can be a biatch.