Hi,
I got exactly the same issue . it comes when you do cascading filtering without filling the filed in the proper order (i.e. from left to right, one by one).
In other words, let say you want to filter the taks based on criteria from the 3 comboxes:
(Combobox a) - created by
(Combobox b) - User1
(Combobox c) - Completed
You will have to choose your criteria in the following order: Combobox a then b and finally c.
If you do no respect the order, then the error might appears. I say might because it is not an exact science. Honestly I tried it 3 times and it occurs 2. Don't know why.
Anyway,
Here below a (really!) dirty way to tournaround this issue.
1/ Log into opengoo with the user who faces this issue.
2/ Edit the following file (using FTP access) :
[server] /opengoo /environment /library /database /adapters/AbstractDBAdapter.class.php
3/ Edit line 385-386 like this
BEFORE: if($query_result === false) {
throw new DBQueryError($sql, $this->lastErrorCode(), $this->lastError());
}
AFTER: if($query_result === false) {}
Save
4/ Go back to opengoo , refresh and change the filtering criteria
5/ Go back to the file you modified (using FTP access):
Edit line 385-386 back to its initial state with the command in the bracket.
You're done
What we basically do, is to prevent the SQL error to appear and hide the filtering Combobox. This allows us to correct the bad filtering.
Regards,