<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Notepad descriptions showing as base64 encoded strings</title> 
  <pubDate>Fri, 10 Apr 2026 00:42:20 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/14204</link> 
  <atom:link rel="self" type="application/rss+xml" title="Notepad descriptions showing as base64 encoded strings" href="https://bugs.horde.org/ticket/14204/rss" /> 
  <description>Notepad descriptions showing as base64 encoded strings</description> 
 
   
   
  <item> 
   <title>One user here had created Notepad&#039;s (Kolab object folders) v</title> 
   <description>One user here had created Notepad&#039;s (Kolab object folders) via Horde3 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&#039;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?</description> 
   <pubDate>Thu, 17 Dec 2015 11:09:53 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/14204#t89195</link> 
  </item> 
   
  <item> 
   <title>
In the SQL backend? Not sure what that would have to do wi</title> 
   <description>
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.</description> 
   <pubDate>Thu, 17 Dec 2015 14:56:15 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/14204#t89198</link> 
  </item> 
   
  <item> 
   <title>Probably dup of Bug: 14199</title> 
   <description>Probably dup of Bug: 14199</description> 
   <pubDate>Thu, 24 Dec 2015 21:44:23 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/14204#t89255</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
