6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
10/17/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#10925] Trying harder to display broken messages
*
Your Email Address
*
Spam protection
Enter the letters below:
. ..___. __..__.. . |__| | (__ [__]| | | | | .__)| ||__|
Comment
> Okay, this problem is two-fold and in > Horde_String::_convertCharset(). First of all, $from is empty, which > is causing iconv() and mb_convert_encoding() to raise errors. I'm > going to further track this down. > But then there seems to be some problem with my PHP, or at least the > PHP documentation. Inside the error handler, error_reporting() is > supposed to return 0 if the command that caused the error is prefixed > with @, which we do when calling @iconv(). error_reporting() still > returns the error level for me though, so we don't return false from > the error handler, thus $php_errormsg is not set in > _convertCharset(), and we don't try mb_convert_encoding() (which > would succeed if we tried that). > Do you use iconv at all? If yes, does calling iconv() from that > message returns an error for you too? If yes, is it because $from is > empty, and does error_reporting() indeed return 0 in the error > handler?
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers