Opened 11 years ago

Closed 10 years ago

Last modified 7 years ago

#697 closed bug (fixed)

headers already sent by (output started at /home/bwrox/ in /home/bwrox/ on line 59

Reported by: guaka Owned by:
Priority: critical Milestone: Legacy Resolved
Component: FrameWork Keywords:
Cc: jeanyves

Description gives

Warning: Cannot modify header information - headers already sent by (output started at /home/bwrox/ in /home/bwrox/ on line 59

Same for

Change History (9)

comment:1 Changed 11 years ago by guaka

  • follow_up changed from none to release

r6040 is a quick fix on alpha is down, and my local install doesn't work either.

comment:2 Changed 10 years ago by feuerdaemon

Whats about this ticket?

comment:3 Changed 10 years ago by jeanyves

It was fix in Test but not in alpha (where code is slighty different)

I have fixed it in Alpha this is to test (for info : this was extra spaces after the ?> in the viewcomment). Problem is that viewcomment in alpha differs from the one in production ...

I have tested it in Alpha and it works.

I prepared manually the same fix in production (removing the extra space + I move a function link_render which was also crearing weird problems).

So situation is that it is fixed everywhere. I am going to commit it in production

comment:4 Changed 10 years ago by globetrotter_tt

  • follow_up changed from release to review code
  • Priority changed from critical to blocker
  • version set to production

this is't fixed yet. On every profile, except my own i get this error:

Fatal error: Class 'LinkSinglePictureLinkpathWidget' not found in
 /home/bwrox/ on line 30

comment:5 Changed 10 years ago by feuerdaemon

  • Priority changed from blocker to critical

Seems to work in Production. Set to a lower prio level. Can anyone test this again and cloe the ticket?

comment:6 Changed 10 years ago by micha

  • follow_up changed from review code to none
  • Resolution set to fixed
  • Status changed from new to closed

Those nasty errors are all gone with our beautiful new design. Closing ticket.

comment:7 Changed 10 years ago by henri

  • Resolution fixed deleted
  • Status changed from closed to reopened

No Micha, they're not. This error persists in the new design (or at least, in the current version).


ps: can someone get me an account to use TRAC? I have used this fake user 'henri' that Julien mentioned to me, but I'd rather be able to post under my own name.

comment:8 Changed 10 years ago by henri

  • Resolution set to fixed
  • Status changed from reopened to closed

Oh no! Sorry! I should <i>read</i> before respond. This is about another header... forgive me for unncessarily reopening/reclosing this ticket :(


comment:9 Changed 7 years ago by TimLoal

  • Component changed from unknown to FrameWork
  • Milestone changed from unassigned to Legacy Resolved
  • Type changed from unknown to bug
Note: See TracTickets for help on using tickets.