Tickets :: [#14041] length of subject too small for ActiveSync

6.0.0-beta1

3/7/26

Summary	length of subject too small for ActiveSync
Queue	Mnemo
Queue Version	4.2.6
Type	Bug
State	Resolved
Priority	1. Low
Owners	mrubinsk (at) horde (dot) org
Requester	skhorde (at) smail (dot) inf (dot) fh-bonn-rhein-sieg (dot) de
Created	07/03/2015 (3900 days ago)
Due
Updated	07/14/2015 (3889 days ago)
Assigned	07/07/2015 (3896 days ago)
Resolved	07/13/2015 (3890 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

07/14/2015 02:36:37 PM	Michael Rubinsky	Comment #8	Reply to this comment
Thanks for the catch. The funny thing is, I thought I DID make the change in import() and didn't even think about replace() :)

07/14/2015 02:35:53 PM	Git Commit	Comment #7	Reply to this comment
Changes have been made in Git (master): commit 2bb252bf58895f061c5e12b8096ce2fa29068911 Author: Michael J Rubinsky <mrubinsk@horde.org> Date: Tue Jul 14 10:34:47 2015 -0400 ~~Bug: 14041~~ Missed this change with last commit. mnemo/lib/Api.php \| 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) http://github.com/horde/horde/commit/2bb252bf58895f061c5e12b8096ce2fa29068911

07/14/2015 02:35:17 PM	Git Commit	Comment #6	Reply to this comment
Changes have been made in Git (FRAMEWORK_5_2): commit 54f72de877749777f11fabcfe94950b5fc02d6c6 Author: Michael J Rubinsky <mrubinsk@horde.org> Date: Tue Jul 14 10:34:47 2015 -0400 ~~Bug: 14041~~ Missed this change with last commit. mnemo/lib/Api.php \| 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) http://github.com/horde/horde/commit/54f72de877749777f11fabcfe94950b5fc02d6c6

07/14/2015 09:51:45 AM	skhorde (at) smail (dot) inf (dot) fh-bonn-rhein-sieg (dot) de	Comment #5	Reply to this comment
It looks like the same problem exists in function import() in the very same file some lines above.

07/13/2015 08:28:30 PM	Michael Rubinsky	State ⇒ Resolved

07/13/2015 08:25:28 PM	Michael Rubinsky	Comment #4	Reply to this comment
...and in master: https://github.com/horde/horde/commit/4dfa0dc13591e038703878ec006ec58903560063 https://github.com/horde/horde/commit/0c839d3cec12502a52be19cbb8b0a02e7ff09516

07/13/2015 08:25:07 PM	Git Commit	Comment #3	Reply to this comment
Changes have been made in Git (FRAMEWORK_5_2): commit e341ef109cbb50a3e474365704a2d07b882162a2 Author: Michael J Rubinsky <mrubinsk@horde.org> Date: Mon Jul 13 16:07:43 2015 -0400 ~~Bug: 14041~~ Add migration to fix the size of the desc field. mnemo/migration/8_mnemo_fix_desc_size.php \| 39 +++++++++++++++++++++++++++++ 1 files changed, 39 insertions(+), 0 deletions(-) http://github.com/horde/horde/commit/e341ef109cbb50a3e474365704a2d07b882162a2

07/13/2015 08:25:02 PM	Git Commit	Comment #2	Reply to this comment
Changes have been made in Git (FRAMEWORK_5_2): commit 1556e70a21559783b7e12cde4d213a532594700b Author: Michael J Rubinsky <mrubinsk@horde.org> Date: Mon Jul 13 16:18:29 2015 -0400 ~~Bug: 14041~~ Trim the incoming activesync memo's description field. The field is technically unlimited, but Mnemo's storage backend may not be. Limit to a reasonable 255. This field is normally taken from the first 64 characters of the memo's text. mnemo/lib/Api.php \| 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) http://github.com/horde/horde/commit/1556e70a21559783b7e12cde4d213a532594700b

07/07/2015 02:57:28 AM	Michael Rubinsky	Assigned to Michael Rubinsky State ⇒ Assigned

07/03/2015 06:32:37 AM	skhorde (at) smail (dot) inf (dot) fh-bonn-rhein-sieg (dot) de	Comment #1 Milestone ⇒ State ⇒ Unconfirmed Patch ⇒ No Queue ⇒ Mnemo Summary ⇒ length of subject too small for ActiveSync Type ⇒ Bug Priority ⇒ 1. Low	Reply to this comment
Task & Notes tries to sync a note with a pretty long subject, but fails due to: 2015-07-02T14:16:48+02:00 INFO: [15170] Horde_Core_ActiveSync_Driver::changeMessage(@Notes@, ...) 2015-07-02T14:16:48+02:00 ERR: SQLSTATE[22001]: String data, right truncated: 7 ERROR: value too long for type character varying(64) 2015-07-02T14:16:48+02:00 ERR: [15170] Change message failed when updating Michael J Rubinsky answered in the thread http://lists.horde.org/archives/horde/Week-of-Mon-20150629/054448.html "... there was a limit on that field in the protocol, but I just verified this is not the case - the field is unlimited."