• Hi,

    am I right that the (core) files of WordPress – in my case e.g. wp-config.php – must be saved with the charset UTF8 without BOM?

    I searched and searched e.g. for a white space or a “hidden special char” fter this “well-known” message had occurred the first time:

    headers already sent by (output started at …/wp-config.php:1) …

    Only after copying the content of this file into a new one without BOM, this “ugly” error message doesn’t appear anymore and I can move on …

    … using UltraEdit where I have disabled this option:

    https://s20.directupload.net/images/240401/mhrbty5p.jpg

    Thanks, temp

Viewing 1 replies (of 1 total)
  • Yes, the files should be saved with UTF8 without BOM. wp-config.php is not really a core file. It contains the individual configuration for the website and is either generated by the installation setup or created manually. Which of these was done for you?

Viewing 1 replies (of 1 total)
  • The topic ‘UTF8 with(out) BOM’ is closed to new replies.