fabiano.mtt Posted November 21, 2013 Share Posted November 21, 2013 I duplicated a website from an hosting (aruba) to another one (a2 hosting) All looks well imported and a2 says that they don't see any error, but I saw a blank page both in the front end and in back end of the new website. we set: ini_set('display_errors', 'on'); on config.inc.php and actually the site reports this 2 errors From the front-end Warning: Cannot modify header information - headers already sent by (output started at /home/velascas/public_html/config/settings.inc.php:1) in /home/velascas/public_html/classes/shop/Shop.php on line 389 From the back-end Warning: Cannot modify header information - headers already sent by (output started at /home/velascas/public_html/config/settings.inc.php:1) in /home/velascas/public_html/classes/Tools.php on line 141 Checking settings.inc.php everything seems right, I don’t know if it can be due to any different type of configuration from the previous server to this new one, have you got any clue? Link to comment Share on other sites More sharing options...
a2hosting-andy Posted November 21, 2013 Share Posted November 21, 2013 Hello, this has been answered many times - your settings.inc.php is likely not encoded UTF8 - see this post: http://www.prestashop.com/forums/topic/83462-solvedwarning-cannot-modify-header-information/?do=findComment&comment=557526 Link to comment Share on other sites More sharing options...
redmeteoric Posted March 22, 2014 Share Posted March 22, 2014 Try this one This is commonly known as the "whitespace problem".The error message typically looks something likeWarning: Cannot modify header information - headers already sent by (output started at /path/to/geeklog/public_html/config.php:581) in /path/to/geeklog/public_html/system/lib-sessions.php on line 180(line numbers and file names may vary). The problem is that many editors seem to add additional blanks (spaces) and/or empty lines at the end of a file when you edit it. This so-called whitespace is then sent to the browser when the file is loaded and interferes with the header of a page that Geeklog tries to send to the browser, often causing problems such as login problems.The fix is, obviously, to remove that whitespace from the file. Read the error message carefully. It says "output started at ..." followed by a file name and a line number. That is the file (and line) that you need to edit. Ignore the second file name - that is only a file that included the file that has the whitespace. The first file is the one you have to edit, not the second one.Since the editor you've been using caused this problem in the first place, you should use another editor to fix the problem and remove the whitespace. https://www.geeklog....hp?op=view&t=38 Link to comment Share on other sites More sharing options...
Recommended Posts