Error with reports view page

[mrashad10]

Hi
When I try to access the "reports/view" page "ushahidi/reports/view/2#" using Ushahidi-2.7 , I get this error message:

---

Kohana_Database_Exception

system/libraries/drivers/Database/Mysqli.php [159]:

---

I have work around this error by comment out that line like this:

---

// throw new Kohana_Database_Exception('database.error', $this->link->error.' - '.$sql);

---

[rjmackay]

Whats the rest of the error message? That should go on to show you a database error.
Your work around doesn't solve the problem, it simply hides the message. But the DB error still happens.

[aoduor]

hey @rjmackay, noticed we're getting lots of people with this error. Probably has something to do with the fact that we changed the default db connection type from mysql to mysqli?

[aoduor]

See also #1178,

[rjmackay]

@aoduor not really. This could be ANY sql error at all. All SQL errors are thrown from system/libraries/drivers/Database/Mysqli.php. If they're not giving us the query we simply can't debug this at all.

[mrashad10]

Hi @rjmackay and @aoduor , first of all I'm sorry for late, I just didn't see the mail till now

@rjmackay there is no "rest of the error message" that message is all what I have!!!!
The error was happens each time I try to reach one of the reports, just that simple.

[aoduor]

Thanks @mrashad10 . @rjmackay, we've got several issues over the past few weeks of a similar nature (the kohana exception), from different unrelated areas within the platform, which aren't replicable and seem to be isolated to these few deployments that keep reporting them. Hunch i had was it could have something to do with the mysqli extension not installed on their servers, but its just a hunch :). I'll search around for the rest and bundle them up for you to have a look at.

[mrashad10]

I forget to tell you that my platform is "XAMPP for Linux 1.7.1", sorry for that.
I know it's old platform but it works will for me and I don't have to update it for now.

[rjmackay]

I can't get this to reproduce on my local install. @mrashad10 does this happen on all reports or just some of them?
Was there anything that changed before the error started happening?
Are you using table prefixes? Are you using custom fields?

Can you change this line in index.php and see if you get a more detailed error?
define('IN_PRODUCTION', TRUE); to define('IN_PRODUCTION', FALSE);

@aoduor If you can reproduce the error, can you digg in and find out more info?
for example, its pretty simple to disable/enable mysqli and see if that has any effect.
If it was a mysqli extension issue we would be seeing a failure on EVERY single page though. I still think this is an SQL error, its just for some reason its not outputting the actual mysql query.

[rjmackay]

Also couldn't find any other mysqli exceptions in github issues - maybe I searched for the wrong thing?

[mrashad10]

Hi
I'm sorry I can't follow this issue any more, our working plan changed and we don't use this application any more.
I hope you the best and keep the good work.

Thank you

[rjmackay]

Not enough info to debug - closing