ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Heater problem - can't find any white spaces

November 24, 2013 5:39am

Subscribe [2]
  • #1 / Nov 24, 2013 5:39am

    überfuzz

    350 posts

    I’m tinkering with a site that’s quite old by now. It’s based on codeigniter 1.7. Now I get this message:

    A PHP Error was encountered

    Severity: Warning

    Message: Cannot modify header information - headers already sent by (output started at xxxxxx/application/config/config.php:1)

    Filename: libraries/Session.php

    Line Number: 662

    When I google this topic everyone point towards possible white spaces in the referred file. But I can’t find any in my config-file. I’m pretty sure this was honky dory when I did the site. Any suggestions on what I should search for errors..?

    Cheers!

  • #2 / Nov 24, 2013 7:28am

    Tpojka

    384 posts

    I remember bugs related to byte ordering mark.
    What W3C says with example.
    I started from this page, but you could find more sources very easy.
    Try to save (custom made) file(s) without bom.

  • #3 / Nov 24, 2013 7:34am

    überfuzz

    350 posts

    Try to save (custom made) file(s) without bom.

    What do you mean?

  • #4 / Nov 24, 2013 7:50am

    Tpojka

    384 posts

    Find all files that are included in runtime (controller, model, custom made helper, custom made library…) and encode it to UTF-8 without BOM. In Notepad++ it is in Menu Encoding. Than save the file.

    edit: or try it with config.php file first.

  • #5 / Nov 24, 2013 10:24am

    überfuzz

    350 posts

    ...and encode it to UTF-8 without BOM.

    Sry for being such a noob about this, but whats a BOM?

    Edit, by the way, is it possible to turn off warnings?

  • #6 / Nov 24, 2013 10:38am

    Tpojka

    384 posts

    Just google for BOM. At wiki there is text too.
    I am not an expert but witnessed saving file as UTF-8 without BOM could solve that problem.
    I pointed how to set it in Notepad++, but every editor should have option for formating edited file(s).

    For disabling warnings, you have to set code in index.php (the root one) with some of wanted levels.

  • #7 / Nov 24, 2013 12:34pm

    überfuzz

    350 posts

    Hmm.. It seems it was an upper/lower case letter issue. When I change the meta casting from: charset=utf-8 to charset=UTF-8 the warning vent away.

    However, now some characters are �. An thought on that..?

  • #8 / Nov 24, 2013 12:48pm

    überfuzz

    350 posts

    No hold it…

    I tried to duplicate the error, so I changed back and forth between lower and upper case. The issue is back, no matter how I set up the charset in the config-file.

  • #9 / Nov 24, 2013 1:38pm

    Tpojka

    384 posts

    I am assuming that you are talking about line in config.php:

    $config['charset'] = 'UTF-8';

    I was not talking about that in posts before, but I was talking about this:

    1. download application/config/config.php
    2. open it in Notepad++*
    3. go to encoding menu
    4. convert to UTF-8 without BOM
    5. save file
    6. upload and replace

    *already said other rich editors have their options, but I can point on Notepad++ now

    That is what I suggested in my first post too.
    Why don’t you try?

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases