[Tickets #9283] Re: Blank screen on Save Draft or Message Send

bugs at horde.org bugs at horde.org
Sun Oct 31 02:42:15 UTC 2010


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

Ticket URL: http://bugs.horde.org/ticket/9283
------------------------------------------------------------------------------
  Ticket             | 9283
  Updated By         | ehymel at e-medico.com
  Summary            | Blank screen on Save Draft or Message Send
  Queue              | IMP
  Version            | 4.3.8
  Type               | Bug
  State              | No Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


ehymel at e-medico.com (2010-10-30 22:42) wrote:

> Probably will need to manually enter PHP debug statements in  
> imp/compose.php to determine where in the script it is breaking  
> and/or whether the script is being loaded at all.

I can't tell that the script is loading at all after I hit either  
"Send Message", "Save Draft", or "Cancel Message".  If I just add an  
"echo 'blah';" command at the start of the script, then I never see my  
'blah', just a blank screen.

Perhaps another clue, though not sure what it means since I don't know  
how imp is working... in my apache logs, if I'm on a windows box using  
either IE or FF, if I navigate to the "New Message" screen then click  
"Cancel Message", I consistently see 3 hits on the server, something  
like this:

192.168.0.187 - - [30/Oct/2010:21:34:04 -0500] "GET  
/imp/mailbox.php?mailbox=INBOX HTTP/1.1" 200 17221
192.168.0.187 - - [30/Oct/2010:21:34:05 -0500] "POST  
/imp/compose.php?uniq=3sk5f8g600o HTTP/1.1" 302 26
192.168.0.187 - - [30/Oct/2010:21:34:05 -0500] "GET  
/imp/mailbox.php?mailbox=INBOX HTTP/1.1" 200 17221

BUT, if I'm on my fedora box (in Firefox of course) and do the same  
sequence, I only see one hit on my server:

192.168.0.186 - - [30/Oct/2010:21:01:49 -0500] "POST  
/imp/compose.php?uniq=119rbuz1teyo HTTP/1.1" 200 6855

Note the different response codes (302 when all works versus 200 when  
it doesn't) for the imp/compose.php script.

Hopefully this helps someone figure this out. I'm happy to do more  
testing if anyone has ideas.






More information about the bugs mailing list