Redirect could not be issued due to headers already being sent. Halting execution for security. Search http://docs.elgg.org/ for more information.

I need help as to why this is happeing

SecurityException Object
(
[message:protected] => Redirect could not be issued due to headers already being sent. Halting execution for security. Search http://docs.elgg.org/ for more information.
[string:private] => exception 'SecurityException' with message 'Redirect could not be issued due to headers already being sent. Halting execution for security. Search http://docs.elgg.org/ for more information.' in /home/cking73/public_html/social/engine/lib/elgglib.php:151
Stack trace:
#0 /home/cking73/public_html/social/actions/admin/plugins/deactivate.php(50): forward()
#1 /home/cking73/public_html/social/engine/lib/actions.php(99): include('/home/cking73/p...')
#2 /home/cking73/public_html/social/engine/handlers/action_handler.php(20): action('admin/plugins#n...')

  • most likely some 'corrupt' language files or 'badly' written plugins code.. that let 'whitespaces thru' which will eventually be interpreted as 'header text' - the exact code spots  will need manual reviews on your server/ execution.. it's usually easier to fix this than to explain details to someone not at coding level.. Elgg blocks this as that 'security exception' because of the dangers of injections.

  • o.k. how would you fix it the plug in is the socia rollover or ocall information service when ever i activate either one of the fata error happens were at in the code should i ook at i have a itte bit of experience just not enough trying to learn

  • a)   ' ..socia rollover or ocall information service.. ' 
            do not compute ;-)  
            what are these ?? 
    b)     ' how would you fix it.. '  
            i) i do not  know that the poblem is caused by any particular plugin.. yet. 
            one needs to be 'reading your mind/code and/or looking over your shoulders'    
            to know what code is active at the time the 'error' happens ;-)  
            ii) some luck maybe or very smart looking at the error symptoms can give a good 'guess' 
            otherwise - good old fsshioned 'debugging' into the code. 
            the usual suspects have been mentioned and discusssed out here various topics before; 
            iii) knowing the sequential history of what has happened, plgugins added, subtracted  
            recently on yr site will help to get closer...  
            hope that you're getting the clear idea ok that what's needed ->  
            is seen by your eyes right now more than anyone else's ;-)  

    * have you recently added/ moved plugins ?  
    * any language file changes ?  

    now that i've spent a good 5-10 minutes of my life thinking and typing all this in..
    let us hope that you will reciprocate with at least the same effort
    or 2x for your next post/question.. more than say just 2 sentences !;-P 


     

     

     

  • Why not to pull in something like that: https://github.com/Elgg/Elgg/pull/5200 and make debugging this problem much more straightforward? It comes again and again..