| Summary | Notepad descriptions showing as base64 encoded strings |
| Queue | Mnemo |
| Queue Version | 4.2.8 |
| Type | Bug |
| State | Duplicate |
| Priority | 1. Low |
| Owners | |
| Requester | mike.gabriel (at) das-netzwerkteam (dot) de |
| Created | 12/17/2015 (3490 days ago) |
| Due | |
| Updated | 12/24/2015 (3483 days ago) |
| Assigned | 12/17/2015 (3490 days ago) |
| Resolved | 12/24/2015 (3483 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
Bug: 14199State ⇒ Feedback
In the SQL backend? Not sure what that would have to do with the data
in Kolab, but the only thing that has changed recently there is
updating the size of the description field in the schema. That, and
some html2text conversions/size trimming when synchronizing via
ActiveSync. Neither of which should cause any data to be base64 encoded.
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Mnemo
Summary ⇒ Notepad descriptions showing as base64 encoded strings
Type ⇒ Bug
State ⇒ Unconfirmed
a while back.
Then the user account got migrated to Horde5, fresh database, old
Kolab backend with existing folders/objects.
Some days ago, he made me aware of the descriptions of Notepad's was
showing a base64 encoded string (instead of a human-readable
description for the Notepad).
Decoding that base64 encoded string resulted in the original description text.
With latest Mnemo version, I can change description and notepad name
in various ways, the base64 encoded description does not return.
Is it possible, that the storage format for Notepad descriptions
(which end-up in the Horde SQL DB, not in the Kolab backend somewhere)
has changed some time recently?