[Tickets #12232] Re: PHP ERROR: array_flip(): Can only flip STRING and INTEGER values! on line 182 of framework/Imap_Client/lib/Horde/Imap/Client/Ids.php
noreply at bugs.horde.org
noreply at bugs.horde.org
Sun May 5 09:01:48 UTC 2013
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/12232
------------------------------------------------------------------------------
Ticket | 12232
Updated By | tomi.orava at ncircle.nullnet.fi
Summary | PHP ERROR: array_flip(): Can only flip STRING and
| INTEGER values! on line 182 of
| framework/Imap_Client/lib/Horde/Imap/Client/Ids.php
Queue | Synchronization
Version | Git master
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
tomi.orava at ncircle.nullnet.fi (2013-05-05 09:01) wrote:
>>> Can you provide a stack trace and/or the value of $this->_ids when
>>> you get this error?
>>
>> Ok, this seems to describe why the flip doesn't work ---> on windows
>> client device
>
> BTW, you can simply use print_r($this->_ids, true) to get a
> printable copy of the array values - or better yet, use
> Horde::debug($this->_ids); and this will output to a file named
> horde_debut.txt in your server's tmp directory.
>
> This doesn't explain why the flip doesn't work. They are both
> arrays. The error complains that the value is NOT an array. We need
> both the value of the ids array as well as the backtrace when it
> doesn't equal an array. You can get a backtrace via either
> debug_bactrace() or just use Horde::debug which automatically
> generates it.
Ok, thanks for the pointers. Here is some more info & backtrace:
2013-05-05T11:39:18+03:00 DEBUG: Variable information:
array(19) {
[0]=>
array(2) {
["read"]=>
int(0)
["flagged"]=>
int(0)
}
[1]=>
int(43400)
[2]=>
int(43405)
[3]=>
int(43421)
[4]=>
int(43422)
[5]=>
int(43423)
[6]=>
int(43424)
[7]=>
int(43425)
[8]=>
int(43426)
[9]=>
int(43427)
[10]=>
int(43429)
[11]=>
int(43431)
[12]=>
int(43432)
[13]=>
int(43433)
[14]=>
int(43440)
[15]=>
int(43441)
[16]=>
int(43442)
[17]=>
int(43443)
[18]=>
int(43444)
}
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() horde/rpc.php:156
2. Horde_ActiveSync->handleRequest()
framework/Rpc/lib/Horde/Rpc/ActiveSync.php:141
3. Horde_ActiveSync_Request_Base->handle()
framework/ActiveSync/lib/Horde/ActiveSync.php:848
4. Horde_ActiveSync_Request_Sync->_handle()
framework/ActiveSync/lib/Horde/ActiveSync/Request/Base.php:236
5. Horde_ActiveSync_Sync->init()
framework/ActiveSync/lib/Horde/ActiveSync/Request/Sync.php:375
6. Horde_ActiveSync_State_Sql->getChanges()
framework/ActiveSync/lib/Horde/ActiveSync/Sync.php:149
7. Horde_Core_ActiveSync_Driver->getServerChanges()
framework/ActiveSync/lib/Horde/ActiveSync/State/Sql.php:825
8. Horde_ActiveSync_Imap_Adapter->getMessageChanges()
framework/Core/lib/Horde/Core/ActiveSync/Driver.php:648
9. Horde_Imap_Client_Ids->__construct()
framework/ActiveSync/lib/Horde/ActiveSync/Imap/Adapter.php:328
10. Horde_Imap_Client_Ids->add()
framework/Imap_Client/lib/Horde/Imap/Client/Ids.php:82
11. Horde::debug() framework/Imap_Client/lib/Horde/Imap/Client/Ids.php:180
More information about the bugs
mailing list