It's exactly the same logic - that makes no sense, and isn't broken 
for anyone else. Are you by chance using the suhosin patch?

Gotcha.



There's definitely history for the ticket that was fetched.



I fixed the problem by changing line 951 from



    for ($i = 0, $iMax = count($history); $i < $iMax; ++$i) {



to



        $count = count($history);

         for ($i = 0; $i < $count; $i++) {





which is basically the same logic except for the $i++ portion.



Queue name and all other history info display fine now.

The date you last ran cvs update was what I had in mind. Sounds pretty 
recent if your sql driver was updated 7 days ago.



If the for loop doesn't execute that means no history was fetched, 
which probably means there was a database error just above - is there 
anything in your Horde log? Have you run the update scripts from 
whups/scripts/upgrades/ ?

Fair enough.



As to version info, Whups has been 1.0-cvs for as long as I can 
remember so you'll have to educate me on where I can find a build # 
for the application.



With respect to the offending whups/lib/Driver/sql.php file, it's 
version 1.282 dated 2008/01/02.



Cheers!





Paul

Whups isn't released for Horde 3.1.x, so you may want to try Horde 
3.2-RC1. And please be more specific than "recent" when talking about 
a HEAD application.

The name of the queue does not display in the History section when 
viewing an existing ticket: the area after Queue=> is blank.



The problem is in file /whups/lib/Driver/sql.php at line 951. The for 
loop is not executing.



         for ($i = 0, $iMax = count($history); $i < $iMax; ++$i) {



Using Horde 3.1.5 and a recent Whups build from CVS.



Thanks much



Paul