[Tickets #9586] Re: Error adding attachment - Internet Explorer 7 - script error in compose.php and incomplete source sent to client

[bugs at horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/h/whups/ticket/9586
------------------------------------------------------------------------------
  Ticket           | 9586
  Aktualisiert Von | wagler at mediaserve.de
  Zusammenfassung  | Error adding attachment - Internet Explorer 7 - script
                   | error in compose.php and incomplete source sent to client
  Warteschlange    | IMP
  Version          | 4.3.9
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


wagler at mediaserve.de (2011-02-21 12:28) hat geschrieben:

> Can you please explain again, which steps in which order exactly you  
> do, and what happens when? What you write is very confusing.

1. We click the button to create a new email.

2. The popup windows opens and we enter the recipients email address.

3. Then we select a file from our hard disk. This is a Microsoft Word  
document with a ".doc" extension. After clicking the refresh button  
(in german: "Aktualisierung") the page is beeing reloaded.

4. At the top of the page there are a huge number of question marks in  
one line, which is not normal. Below the message for the successfully  
added attachment is displayed (in german: ""Test.doc" als Anhang  
hinzugefügt.
"). The Microsoft Internet Explorer is also showing a script error on  
the page (in german: "Fehler auf der Seite").
Despite of that the source sent to the client is incomplete, because  
it begins with the question marks, followed by a number of HTML  
"script" tags and the rest of the source.
It is not possible to send the email by clicking the appropriate button.

There are no errors in the horde log or the PHP error log.
The real problem seems to be the incomplete (or cut) source generated  
and sent to the client, because the file was successfully attached.
We are using the latest version of PHP 5.2