On most Gentoo Systems only MySQL 5 is installed, but dotproject relies on MySQL 4. Some fixes are required to get dotproject working with MySQL 5, which are available through http://www.pienotech.com/dotproject_201_mysql5.patch
This patch doesn't seem to be required for dotproject-2.0.4. Could you retest, please? Many thanks, Stu
This patch is indeed a bit old, but it *is* needed in version 2.0.4 as well. It doesn't apply on file modules/projects/vw_logs.php, but I think this is a typo in the patch (removed the newline at the end of the file). If you don't apply the patch you'll get a lot of mysql-errors on the "tasks view".
wolf31o2: you mentioned using dotproject, so perhaps you can shed some light on this bug?
I just tried the patch and it seems to have fixed the problem I was having with dotproject-2.0.4. I have mysql-5.0, dotproject-2.0.4, php-5.2.1-r3, apache-2.0.58-r2. I do not see the same error that's reported here: http://www.dotproject.net/vbulletin/archive/index.php/t-2253.html and very similar errors when you click the Task link at the top of the page. nova dotproject # patch -p1 < ~/dotproject_201_mysql5.patch patching file classes/query.class.php Hunk #1 succeeded at 428 with fuzz 1. Hunk #2 succeeded at 446 (offset 2 lines). patching file modules/projects/vw_logs.php Reversed (or previously applied) patch detected! Assume -R? [n] y Hunk #1 succeeded at 174 (offset 7 lines). patching file modules/tasks/tasks.php Hunk #1 FAILED at 174. 1 out of 2 hunks FAILED -- saving rejects to file modules/tasks/tasks.php.rej patching file modules/tasks/todo.php patching file modules/tasks/view.php Hunk #1 succeeded at 73 (offset 5 lines).
That should read: After I applied the patch, I no longer see the error reported here: http://www.dotproject.net/vbulletin/archive/index.php/t-2253.html and other reported SQL errors when one would click the Task link at the top of the dotproject page.
I get the same errors. While I use dotproject, I know very little of its internals. I'd much rather the thing work than have to dig into it. ;] I can test the patch, if necessary, but I won't be of much use to anyone as far as debugging this otherwise due to both time constraints and my lack of familiarity with the software in anything but a user role.
Let's revisit this when upstream gets around to fixing this properly.