| Summary | Reply to message generates array to string error |
| Queue | IMP |
| Queue Version | 4.0.3 |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | ben (at) cpanel (dot) net |
| Created | 05/02/2005 (7391 days ago) |
| Due | |
| Updated | 05/02/2005 (7391 days ago) |
| Assigned | |
| Resolved | 05/02/2005 (7391 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
bug 1835.State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Reply to message generates array to string error
Queue ⇒ IMP
New Attachment: Horde_array_to_string_in_reply.patch
/usr/local/cpanel/base/horde/imp/lib/Compose.php on line 769
Apparently the '/%m/' array element in $match is a blank array. Seems
to only occur on one of the messages in the inbox. Here's the array
element:
/* Message-ID. */
'/%m/' => $h->getOb('message_id'),
I patched our Compose.php with this line before the preg_replace:
if (!$match['/%m/']) { $match['/%m/'] = ''; }
It's a silly hack, but prevents the issue from manifesting in the
user's browser. I suspect that it's really an issue with PHP's
imap_headerinfo.
Using PHP 4.3.10
Patch is attached.