MySQL 4.0.12 Problem

MySQL 4.0.12 Problem

am 31.03.2003 00:01:05 von Craignet

------=_NextPart_000_0005_01C2F710.3E271000
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi

I have a phpnuke website that works fine with 3.23.55

if I install 4.0.4 version of Mysql server it still works ok

When I install 4.0.10 or 4.0.12 I get errors with phpnuke. As soon as I =
revert back to a previous version that works, all is fine again.

Can you help? It is probably phpnuke at fault but why does it happen =
with the new versions only. Am I mising something simple?

Here are the errors I get for reference

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL =
result resource in C:\Program Files\Apache =
Group\Apache2\htdocs\tuselp\includes\sql_layer.php on line 301

Warning: main(language/lang-.php) [function.main]: failed to create =
stream: No such file or directory in C:\Program Files\Apache =
Group\Apache2\htdocs\tuselp\mainfile.php on line 79

Warning: main() [function.main]: Failed opening 'language/lang-.php' for =
inclusion (include_path=3D'.;c:\php4\pear') in C:\Program Files\Apache =
Group\Apache2\htdocs\tuselp\mainfile.php on line 79

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL =
result resource in C:\Program Files\Apache =
Group\Apache2\htdocs\tuselp\includes\sql_layer.php on line 301

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL =
result resource in C:\Program Files\Apache =
Group\Apache2\htdocs\tuselp\includes\sql_layer.php on line 301

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL =
result resource in C:\Program Files\Apache =
Group\Apache2\htdocs\tuselp\includes\sql_layer.php on line 357

Warning: head(themes//theme.php) [function.head]: failed to create =
stream: No such file or directory in C:\Program Files\Apache =
Group\Apache2\htdocs\tuselp\header.php on line 52

Warning: head() [function.head]: Failed opening 'themes//theme.php' for =
inclusion (include_path=3D'.;c:\php4\pear') in C:\Program Files\Apache =
Group\Apache2\htdocs\tuselp\header.php on line 52
------=_NextPart_000_0005_01C2F710.3E271000--

Re: MySQL 4.0.12 Problem

am 31.03.2003 01:12:27 von Arjen Lentz

Hi,

On Mon, 2003-03-31 at 08:01, Craignet wrote:
> I have a phpnuke website that works fine with 3.23.55
> if I install 4.0.4 version of Mysql server it still works ok
> When I install 4.0.10 or 4.0.12 I get errors with phpnuke. As soon as
> I revert back to a previous version that works, all is fine again.
>
> Can you help? It is probably phpnuke at fault but why does it happen
> with the new versions only. Am I mising something simple?
>
> Here are the errors I get for reference
>
> Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in C:\Program Files\Apache Group\Apache2\htdocs\tuselp\includes\sql_layer.php on line 301
> Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in C:\Program Files\Apache Group\Apache2\htdocs\tuselp\includes\sql_layer.php on line 301
> Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in C:\Program Files\Apache Group\Apache2\htdocs\tuselp\includes\sql_layer.php on line 301
> Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in C:\Program Files\Apache Group\Apache2\htdocs\tuselp\includes\sql_layer.php on line 357

You'll need to check that file (sql_layer.php) in phpnuke to see what
queries are executed just before those calls to
mysql_fetch_rows()/mysql_fetch_array().

Those queries will be returning an error rather than a result set, and
the phpnuke code obvious does not check for errors everywhere (phpnuke
is not particularly well written in that respect, unfortunately).

You'll want to check the return value coming back from mysql_query(), if
that is 0 you'll want to:
1) print the original query (the query string that is passed to
mysql_query() - if it's in a variable, just print that var, otherwise
change the code to put it in a variable before calling mysql_query() so
you can print it later).
2) the mysql_errno() code.
3) the mysql_error() message.

That will likely give you a clear indication of what the problem is.


Regards,
Arjen.
--
Training,Support,Licenses,T-shirts @ https://order.mysql.com/?marl
Utrecht NL: June 16-20, MySQL & PHP training (in Dutch)
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Arjen G. Lentz
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Technical Writer, Trainer
/_/ /_/\_, /___/\___\_\___/ Brisbane, QLD Australia
<___/ www.mysql.com


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org