codex says "wp-config file should end in ?>" but mine doesn't

  • Hi,

    I’ve just started, and I’m kind of learning as I go. I was following the instructions for editing the wp-config file. It got sketchy at the end, because my version of the wp-config file didn’t have a lot of the lines the instructions were instructing me to edit (such as “define(‘WP_MEMORY_LIMIT’,” or “define(‘EMPTY_TRASH_DAYS’,”). But since the instructions said something about not all versions having every line, I decided to continue.

    At the very end, when the instructions were telling me how to double check for mistakes, it said “The last thing in the file should be ?> and nothing else. No spaces.”

    There was nothing like a “?>” at the end of the code in the file. I never touched the last line of code. Is there something missing?

    And should I worry about all the missing lines?

    Thanks,
    Monica

Viewing 3 replies - 1 through 3 (of 3 total)

  • No. It has been deliberately omitted.

    Thread Starter Monica

    (@monica4567)

    Okay, so the “?>” is out — or you mean all those lines that are missing were omitted? Or both?

    Thanks for the fast response!

    ?> is often deliberately not used at the end of a PHP script. It’s not strictly necessary and including it can cause “headers already sent” warnings in some situations.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘codex says "wp-config file should end in ?>" but mine doesn't’ is closed to new replies.