| Summary | Call to a member function timestamp() on a non-object in /var/www/horde/kronolith/lib/Driver/sql.php |
| Queue | Synchronization |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | anders.lund (at) uninett (dot) no |
| Created | 03/04/2008 (6457 days ago) |
| Due | |
| Updated | 03/07/2008 (6454 days ago) |
| Assigned | 03/06/2008 (6455 days ago) |
| Resolved | 03/07/2008 (6454 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
can't process your complete calendar only to find the issue.
Created a new calendar in Evolution, and tried new sync with this
calendar. This time it worked. So I guess one of my old events create
this problem. Question is which... Perhaps this ticket should just be
closed until I find more exact reason for the error.
can't process your complete calendar only to find the issue.
that causes this error and upload it here?
it here:
http://www.lunders-and.no/sync_log.tgz
Priority ⇒ 2. Medium
State ⇒ Feedback
that causes this error and upload it here?
Queue ⇒ Synchronization
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Call to a member function timestamp() on a non-object in /var/www/horde/kronolith/lib/Driver/sql.php
Queue ⇒ Kronolith
State ⇒ Unconfirmed
seem to trigger some kind of bug in
/var/www/horde/kronolith/lib/Driver/sql.php on line 909.
Using Debian Etch, but upgraded PHP to 5.2.5 from www.dotdeb.org. This
is the version of Kronolith which is bundled in horde-webmail-1.1-rc2,
but I see the same error in the latest CVS checkout I have running on
another server.
In my PHP log I have:
PHP Fatal error: Call to a member function timestamp() on a
non-object in /var/www/horde/kronolith/lib/Driver/sql.php on line 909