| Summary | Search error for 'All Past' and 'All Future' |
| Queue | Kronolith |
| Queue Version | 2.0.3 |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | |
| Requester | csacca (at) thecsl (dot) org |
| Created | 07/12/2005 (7305 days ago) |
| Due | |
| Updated | 07/12/2005 (7305 days ago) |
| Assigned | 07/12/2005 (7305 days ago) |
| Resolved | 07/12/2005 (7305 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
New Attachment: search.patch
head it should apply there too. Wasn't acutally as bad as I though it
was going to be first. I did some testing on my changes (basic event,
recuring event, all day event) and they were good, but a second check
is always useful.
State ⇒ Feedback
personally.
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Search error for 'All Past' and 'All Future'
Queue ⇒ Kronolith
past or all future, I get the following error:
Fatal error: Call to a member function on a non-object in
/usr/share/horde3/kronolith/lib/Driver.php on line 98 (or 97)
Through var_dump()'ing $query, I found that it's because $query->start
or $query->end is set to null. In HEAD, this happend on lines 74-79
of search.php. It seems that you either need to set the values for
->start and ->end to real, though almost infinite times, or build
logic into lib/Driver.php to deal with the case that one of them is
null.
I'd be willing to patch this, but I'm not sure on which way to go.
Thanks,
Chris Sacca