Viewing 4 replies - 1 through 4 (of 4 total)
  • confirmed
    wp-config-sample.php
    lacks the closing php statement

    erm this isn’t a bug.

    [quote]
    The one exception is wp-config.php where it’s best to leave the end tag off due to how easy it is for a novice and their editor to add a trailing
    whitespace.
    [/quote]

    that trailing whitespace can be an issue, and cause the infamous headers already sent message.

    the instructions tell folks to copy wp-config-sample.php to wp-config.php on new installs. maybe not a bug, per se, but definitely a “glitch”

    No necessarily a glitch either, it caught me out the first time I came across it.

    If it is a user editable file, then leaving out the closing php tag is beneficial. I just wish that when they do it, they would leave a note in the file explaining why 🙂

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘BUG: 2.8.2 wp-config-sample.php lacks a ?> at the end!’ is closed to new replies.