hi, in History.php , function getByTimestamp, line 197 it

Fri, 03 Sep 2010 16:08:56 +0000

hi, in History.php , function getByTimestamp, line 197 it should rather read if (!is_integer(intval($ts))) { than if (!is_integer($ts)) { cause the current version fails for strings from syncMl containing integer values

According to the phpdoc, Horde_History#getByTimestamp must b

Fri, 03 Sep 2010 17:31:19 +0000

According to the phpdoc, Horde_History#getByTimestamp must be passed an integer value for $ts. So the question becomes, what is passing the $ts value as a non-integer? Can you provide a backtrace from a call that fails?

Its a String but with a int. Value

Fri, 03 Sep 2010 17:35:25 +0000

Its a String but with a int. Value

> Its a String but with a int. Value Exactly. It needs to

Fri, 03 Sep 2010 18:05:59 +0000

> Its a String but with a int. Value Exactly. It needs to be an int, not a string - at least according to the phpdoc for that method. So the calling code is responsible for making sure the value is cast to an integer...hence the reason I asked for a backtrace, to see where it is being called from.

actually i tried a few ways but i need a howto get horde spi

Sat, 04 Sep 2010 20:21:34 +0000

actually i tried a few ways but i need a howto get horde spit out backtraces

http://us.php.net/debug_backtrace

Sat, 04 Sep 2010 21:00:23 +0000

http://us.php.net/debug_backtrace

well i knew that - still it just outputs a WARN: HORDE [

Sun, 05 Sep 2010 19:09:35 +0000

well i knew that - still it just outputs a WARN: HORDE [horde] Caught output: object(Horde_Registry_Caller)#261 (2) { ["registry:protected"]=> object(Horde_Registry)#6 (10) .... so no proper backtrace as i expected some consequent function calls getting listed

finally! would be a great idea to add full exception cont

Sun, 05 Sep 2010 20:05:01 +0000

finally! would be a great idea to add full exception content to the log for syncml calls as they aren't viewed in a browser had to change in lib/Horde.php line 137 self::logMessage(print_r(html_entity_decode($errortext), true), 'EMERG'); to get it 2010-09-05T22:00:12+02:00 EMERG: HORDE [kronolith]

A fatal error has occurred

The timestamp needs to be an integer!

 1. Horde_Rpc_Syncml->getResponse() /var/www/catchall/htdocs/horde/rpc.php:164
 2. SyncML_ContentHandler->process() /var/www/catchall/htdocs/horde/lib/Horde/Rpc/Syncml.php:56
 3. xml_parse() /var/www/catchall/htdocs/horde/lib/SyncML.php:144
 4. SyncML_ContentHandler->_endElement()
 5. SyncML_ContentHandler->endElement() /var/www/catchall/htdocs/horde/lib/SyncML.php:233
 6. SyncML_ContentHandler->handleCommand() /var/www/catchall/htdocs/horde/lib/SyncML.php:320
 7. SyncML_Command_Final->handleCommand() /var/www/catchall/htdocs/horde/lib/SyncML.php:450
 8. SyncML_State->handleFinal() /var/www/catchall/htdocs/horde/lib/SyncML/Command/Final.php:48
 9. SyncML_Sync->handleFinal() /var/www/catchall/htdocs/horde/lib/SyncML/State.php:408
10. SyncML_Sync->createSyncOutput() /var/www/catchall/htdocs/horde/lib/SyncML/Sync.php:631
11. SyncML_Sync->_retrieveChanges() /var/www/catchall/htdocs/horde/lib/SyncML/Sync.php:387
12. SyncML_Backend_Horde->getServerChanges() /var/www/catchall/htdocs/horde/lib/SyncML/Sync.php:587
13. Horde_Registry_Caller->listBy() /var/www/catchall/htdocs/horde/lib/SyncML/Backend/Horde.php:149
14. Horde_Registry_Caller->__call() /var/www/catchall/htdocs/horde/lib/SyncML/Backend/Horde.php:149
15. Horde_Registry->call() /var/www/catchall/htdocs/horde/lib/Horde/Registry/Caller.php:41
16. Horde_Registry->callByPackage() /var/www/catchall/htdocs/horde/lib/Horde/Registry.php:853
17. call_user_func_array() /var/www/catchall/htdocs/horde/lib/Horde/Registry.php:894
18. Kronolith_Api->listBy()
19. Horde_History->getByTimestamp() /var/www/catchall/htdocs/horde/kronolith/lib/Api.php:500

Details

The full error message is logged in Horde's log file, and is shown below only to administrators. Non-administrative users will not see error details.

[pid 12867 on line 137 of "/var/www/catchall/htdocs/horde/lib/Horde.php"]

in lib/SyncML/Sync.php , function SyncML_Sync needs explicit

Sun, 05 Sep 2010 20:24:48 +0000

in lib/SyncML/Sync.php , function SyncML_Sync needs explicit cats to int

Changes have been made in Git for this ticket: Ensure these

Sun, 05 Sep 2010 20:34:02 +0000

Changes have been made in Git for this ticket: Ensure these are integers Bug: 9217 http://git.horde.org/diff.php/framework/SyncML/SyncML/Command/Alert.php?rt=horde-git&r1=240ff73e2a3bcfe5e5649e5d9153d87b25471d36&r2=b0cd708e710752421205677bc049c195282741ad http://git.horde.org/diff.php/framework/SyncML/SyncML/Sync.php?rt=horde-git&r1=240ff73e2a3bcfe5e5649e5d9153d87b25471d36&r2=b0cd708e710752421205677bc049c195282741ad

Does this help?

Sun, 05 Sep 2010 20:34:24 +0000

Does this help?

yes, this fixed the issue for me

Sun, 05 Sep 2010 20:50:15 +0000

yes, this fixed the issue for me

SyncMl Fails - is_integer issue

hi, in History.php , function getByTimestamp, line 197 it

According to the phpdoc, Horde_History#getByTimestamp must b

Its a String but with a int. Value

> Its a String but with a int. Value Exactly. It needs to

actually i tried a few ways but i need a howto get horde spi

http://us.php.net/debug_backtrace

well i knew that - still it just outputs a WARN: HORDE [

finally! would be a great idea to add full exception cont

A fatal error has occurred

The timestamp needs to be an integer!

Details

The full error message is logged in Horde's log file, and is shown below only to administrators. Non-administrative users will not see error details.

in lib/SyncML/Sync.php , function SyncML_Sync needs explicit

Changes have been made in Git for this ticket: Ensure these

Does this help?

yes, this fixed the issue for me