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

bugs at horde.org bugs at horde.org
Fri Mar 18 11:15:26 UTC 2011


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

Ticket-URL: http://bugs.horde.org/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-03-18 11:15) hat geschrieben:

> This is indeed some kind of a horribly broken page. I have never  
> seen this before. I can only assume that some is awfully wrong with  
> output buffering in your PHP version. Though that still won't  
> explain the question marks.
> Try disabling any output buffering or processing settings in both  
> Horde's and PHP's configuration. Try disable bytecode caches, if you  
> use any. Try pruning the Horde cache storage, if you configured  
> caching in Horde. If everything fails, build a new PHP.

Hello,

I think we could solve the problem:

After activating the "fileinfo" extension the corruption within the  
website's source code is no longer present. The Javascript errors are  
also gone.

Both in the Microsoft Internet Explorer an Mozilla Firefox we are now  
able to successfully attach ".doc" files to a new email. I hope this  
is a permanent "fix" an might help others.

Bye the way: We are not using any accelerator extensions and have no  
output compression handler enabled for this website. Disabling the  
"compress_pages" directive within the horde configuration has not  
solved the problem.







More information about the bugs mailing list