[Tickets #13868] Re: Changes made in kronolith are not send to AS devices.
noreply at bugs.horde.org
noreply at bugs.horde.org
Wed Feb 25 16:31:19 UTC 2015
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: https://bugs.horde.org/ticket/13868
------------------------------------------------------------------------------
Ticket | 13868
Updated By | horde at vdorst.com
Summary | Changes made in kronolith are not send to AS devices.
Queue | Synchronization
Version | FRAMEWORK_5_2
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners | Michael Rubinsky
------------------------------------------------------------------------------
horde at vdorst.com (2015-02-25 16:31) wrote:
I see alot of these in my debug horde_log.
2015-02-25T17:11:54+01:00 DEBUG: HORDE [kronolith] PHP ERROR:
Non-static method Date_Calc::dateDiff() should not be called
statically, assuming $this from incompatible context [pid 1164 on line
115 of "/data/webapps/horde/kronolith/lib/Day.php"]
2015-02-25T17:11:54+01:00 DEBUG: HORDE [kronolith] PHP ERROR:
Non-static method Date_Calc::isValidDate() should not be called
statically, assuming $this from incompatible context [pid 1164 on line
2061 of "/usr/share/php/Date/Calc.php"]
2015-02-25T17:11:54+01:00 DEBUG: HORDE [kronolith] PHP ERROR:
Non-static method Date_Calc::isValidDate() should not be called
statically, assuming $this from incompatible context [pid 1164 on line
2064 of "/usr/share/php/Date/Calc.php"]
2015-02-25T17:11:54+01:00 DEBUG: HORDE [kronolith] PHP ERROR:
Non-static method Date_Calc::dateToDays() should not be called
statically, assuming $this from incompatible context [pid 1164 on line
2067 of "/usr/share/php/Date/Calc.php"]
2015-02-25T17:11:54+01:00 DEBUG: HORDE [kronolith] PHP ERROR:
Non-static method Date_Calc::dateToDays() should not be called
statically, assuming $this from incompatible context [pid 1164 on line
2068 of "/usr/share/php/Date/Calc.php"]
Current entry for "horde_histories_modseq" is
"history_modseq" = "362"
"history_modseqempty" = "0"
I don't know how it is related to "horde_histories"
which has an entry with "history_id" = "955"
More information about the bugs
mailing list