[Tickets #11777] Re: ActiveSync error after latest changes in git
noreply at bugs.horde.org
noreply at bugs.horde.org
Fri Jan 4 21:41:21 UTC 2013
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/11777
------------------------------------------------------------------------------
Ticket | 11777
Updated By | max at grobecker.info
Summary | ActiveSync error after latest changes in git
Queue | Synchronization
Version | Git master
Type | Bug
State | Resolved
Priority | 1. Low
Milestone |
Patch |
Owners | Michael Rubinsky
------------------------------------------------------------------------------
max at grobecker.info (2013-01-04 21:41) wrote:
I have the same problem and debugged a bit:
On my system, every time I try to sync anything (regardless if
calendar, mail or contacts) with my Android phone and one specific
account it got stuck with the exception "_logger is not a valid
property" which probably also caused segfaults.
The code where it happens is in Horde/ActiveSync.php, around line 650.
I can't get the original line numbers since I added some extra debug code.
It is around here, near the bottom of the function handleRequest():
public function handleRequest($cmd, $devId) {
......
$class = 'Horde_ActiveSync_Request_' . basename($cmd);
$version = $this->getProtocolVersion();
if (class_exists($class)) {
$request = new $class($this, $device);
$request->setLogger($this->_logger);
----> $result = $request->handle(); <---- here it crashes
$this->_driver->clearAuthentication();
return $result;
}
I tracked it down to the
Horde_ActiveSync_SyncCache::updateCollection() function. Whenever I
try to access $this->_logger there the whole thing crashes, even when
I just try to make a var_dump() on it.
So I commented out the Logging, cleared the caches, removed the device
from Horde and tried again. Now it stops whith this error:
PHP Fatal error: Cannot use object of type
Horde_ActiveSync_Folder_Collection as array in
/usr/share/pear/Horde/ActiveSync/State/Base.php on line 380
This might be a local problem with my PHP installation which is PHP
5.3.3 on a CentOS 5.x system, but it sound very similar to the problem
of the ticket opener!
More information about the bugs
mailing list