get error 1.4.1 b23 in postnuke

wi777

Joined: 2003-08-05
Posts: 19
Posted: Sat, 2003-08-23 22:10

hi:
here I am again :-)

MySQL 4.0.14 (mdk) + php 4.3.2 + httpd 2.0.47
postnuke 0.726

error msg as the followin is:
========================================================
Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /var/www/html/modules/gallery/classes/database/mysql/Database.php on line 37

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/modules/gallery/classes/database/mysql/Database.php:37) in /var/www/html/includes/pnAPI.php on line 1097
========================================================
take care

 
Tim_j
Tim_j's picture

Joined: 2002-08-15
Posts: 6818
Posted: Sun, 2003-08-24 01:34

Hi,

i can not reproduce this on Apache 1.3.28 ; PHP 4.3.1 ; MySQL 3.23.55 ; postNuke 0.726.

are you sure you did not change something ?
RANDOM BLOCK ?

Regards,

Jens

 
wi777

Joined: 2003-08-05
Posts: 19
Posted: Sun, 2003-08-24 03:24
Tim_j wrote:
Hi,

i can not reproduce this on Apache 1.3.28 ; PHP 4.3.1 ; MySQL 3.23.55 ; postNuke 0.726.

are you sure you did not change something ?
RANDOM BLOCK ?

Regards,

Jens

yes.. I change nls.php which mentioned for utf-8 encoding previous post by me.

 
beckett
beckett's picture

Joined: 2002-08-16
Posts: 3474
Posted: Sun, 2003-08-24 05:48

Are you using PHP-Nuke 6.5 or newer?

If so, then what version of Gallery are you using? You should upgrade to 1.4-RC1 or 1.3.4 if that's not what you have.

That's usually the cause of this specific error message.

-Beckett (

)

 
wi777

Joined: 2003-08-05
Posts: 19
Posted: Sun, 2003-08-24 10:52
beckett wrote:
Are you using PHP-Nuke 6.5 or newer?

If so, then what version of Gallery are you using? You should upgrade to 1.4-RC1 or 1.3.4 if that's not what you have.

That's usually the cause of this specific error message.

-Beckett (

)

1. postnuke is totally not php-nuke. I tried them both.
I don't think php-nuke is better than postnuke.

2. All things I say is cvs ver. of gallery. not release yet.
download cvs here
http://jpmullan.com/galleryupdates/

3. I just report error for development team, not ask request for support.
anyway thank you all

regards

 
Tim_j
Tim_j's picture

Joined: 2002-08-15
Posts: 6818
Posted: Sun, 2003-08-24 11:02

Hi wi777,

if you havent tried this already ...
can you switch to the original nls.php and see if the error is still there ?

Regards,

Jens

 
wi777

Joined: 2003-08-05
Posts: 19
Posted: Sun, 2003-08-24 13:02
Tim_j wrote:
Hi wi777,

if you havent tried this already ...
can you switch to the original nls.php and see if the error is still there ?

Regards,

Jens

here is the method and the reason why I change nls.php charset to unicode utf-8.

http://gallery.menalto.com/index.php?name=PNphpBB2&file=viewtopic&t=8605

If any i18n (internationalization) software development team ever thought a word
with two bit including slash charactor and how can search these words like japanese koreanese chinese thai and so on , it would must be phpbb at first .

believe me, I don't wanna be a translator for utf-8 encoding to increase my site traffic, it's in vain and the days will keep going without me.

Not only gallery but it's a same problem to php-nuke and postnuke also for localization to search slash charactors.

If a site is encoding with utf-8 charset, send utf-8 mail received by client of webmail of users' will be a different charset problem.

Linux mandrake have a solution to this thru urpmi php-mbstring and php-iconv.

if a gallery could not search slash charactor, chinese have many many words includin slash. not only 3 words.
same condition as Japanese and korean
that's the point what I mean.

 
beckett
beckett's picture

Joined: 2002-08-16
Posts: 3474
Posted: Tue, 2003-08-26 05:44
wi777 wrote:
postnuke is totally not php-nuke.

Apologies! I missed that you specified "postnuke 0.726" in your first post. It wrapped to a new line and I didn't see it. I suggested PHP-Nuke because users of PHP-Nuke saw this exact error for the reason I mentioned. So ignore what I said!

So this only pops up when you change the charset encoding? If so, we'll try and sort this out. It's possible we'll need to set all the charsets to UTF-8 then.

-Beckett (

)