proposed release for testing

[Dave Hall]

Hi all,

I have been working on some fixes for the 0.9.16 branch.

There is a tarball at
http://phpgroupware.org/downloads/phpgroupware-0.9.16.014-proposed.tar.bz2

or you can grab it from svn at
svn://svn.sv.gnu.org/phpgroupware/branches/Version-0_9_16-branch

Unless serious issues are found I will push this out during the weekend.
Keep in mind PHP5 support is best effort.

Cheers

Dave

[Giorgio Pioda]

HI

I've done a checkout and tried to upgrade my production server. The only (grave for me) thing that doesn't install is Fudforum. I guess is still the old "reads" vs "readsx" problem for mysql 5.0. Is thare any chance to get this fix for -014 ?

cheers

Giorgio Pioda.

Sent from the phpGroupWare forums @ forums.phpGroupWare.org

[Dave Hall]

Post by Giorgio Pioda
HI
I've done a checkout and tried to upgrade my production server. The
only (grave for me) thing that doesn't install is Fudforum. I guess is
still the old "reads" vs "readsx" problem for mysql 5.0. Is thare any
chance to get this fix for -014 ?

Is there a bug report in for this one?

Cheers

Dave

[Giorgio Pioda]

Yes. It is the
bug #20284 (June 2007!)

The fudforum module is incompatible with mysql 5.0 because the "reads" word is, starting from version 5.0, a reserved word of the SQL instruction set.

I fixed it with a "dirthy quickpatch replacing the "reads" string with "readsx" in the installer script for fudforum (in september 2007) but I didn't propose that patch because I tought that some developper would fix that problem in a clean manner in the sources since the issue was well known....

cheers

gfwp.

Sent from the phpGroupWare forums @ forums.phpGroupWare.org

[Dave Hall]

Post by Giorgio Pioda
Yes. It is the
bug #20284 (June 2007!)
The fudforum module is incompatible with mysql 5.0 because the "reads"
word is, starting from version 5.0, a reserved word of the SQL
instruction set.
I fixed it with a "dirthy quickpatch replacing the "reads" string with
"readsx" in the installer script for fudforum (in september 2007) but
I didn't propose that patch because I tought that some developper
would fix that problem in a clean manner in the sources since the
issue was well known....

As this will require a schema change it will not be including in the
0.9.16 branch. It will be considered for the 0.9.18 release. The bug
report will allow us to track the issue.

Cheers

Dave