[Tickets #10497] Re: Invalid UTF-8 sequence in argument ... /usr/share/php/Horde/Prefs/Scope.php

bugs at horde.org bugs at horde.org
Mon Sep 12 08:13:47 UTC 2011


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10497
------------------------------------------------------------------------------
  Ticket             | 10497
  Updated By         | szimszon at oregpreshaz.eu
  Summary            | Invalid UTF-8 sequence in argument ...
                     | /usr/share/php/Horde/Prefs/Scope.php
  Queue              | IMP
  Version            | 5.0.11
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


szimszon at oregpreshaz.eu (2011-09-12 08:13) wrote:

Yes i upgraded it from previous version. I have now the DB (pgsql):

             Name                   |    Owner   | Encoding  |  
Collation | Ctype |   Access privileges
hordewebmail                | horde       | UTF8      | C         | C     |

What webmail-install asked charset is utf-8...

So if I make a new contact like "Árvízt?r? Tükörfúrógép" in turba I  
can search for it and I can see it with proper encoding... In the db  
dumb I see "Árvízt?r? Tükörfúrógép" too...

But if I impot my key file I see what is like unicode or so:

"Bag A\\164\\164rib\\165\\164es\\012    friendl\\171Name:  
s\\172ims\\172on at oregpresha\\172.e\\165 S\\164ar\\164Com L\\164d.  
a\\172onos\\355\\164\\363ja\\012    localKe\\171ID: AF 76 8E 36 37 78  
4A 4D 1D 34 09 69 A1 28 05 AE 18 02 62 62 \\012Ke\\171  
A\\164\\164rib\\165\\164es: <No  
A\\164\\164rib\\165\\164es>\\012-----BEGIN RSA PRIVATE  
KEY-----\\012Proc-T\\171pe: 4,ENCRYPTED\\012DEK-Info:  
DES-EDE3-CBC,513EC7D887C811DF\\012\\012BENCZY\\167jE29b\\170KqcmdI1OOaDPHrZ/s+1CT7XjQsZ6c\\1679AmlU2DdFBX/9OihNGYNK\\012r\\166CcjXa1ocgqXd\\1677eeY\\17232XATKA3Pm\\165fjYrApMh8YN9maXRD\\167\\172F\\166\\172ZjNmBb/"

So it seems to me that is not an encoding error in db side...



>>         4=\\012-----END CERTIFICATE-----') [pid 21062 on line 801 of
>> "/usr/share/php/Horde/Db/Adapter/Base.php"]
>
> Did you upgrade from a previous version of Horde?  At first glance  
> it looks like you did not properly upgrade your SQL backend charset.  
>  But I'm not the DB expert.






More information about the bugs mailing list