Opened 17 years ago
Closed 16 years ago
#6791 closed enhancement (fixed)
Eliminate closing ?>'s from wp-config-sample.php
Reported by: | Otto42 | Owned by: | |
---|---|---|---|
Milestone: | 2.8 | Priority: | normal |
Severity: | normal | Version: | 2.5 |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
One of the most frequent problems mentioned on the forum is the "blank line" problem. This is where some file contains a blank line before or after the <?php .. ?> tags that causes either header issues (which will prevent login's due to cookies not working) or causes invalid feed issues (which is recently a major problem with FeedBurner, since they stopped accepting invalid feeds).
It is described better here:
http://feedvalidator.org/docs/error/WPBlankLine.html
I recommend eliminating the use of the closing ?> tag in the wp-config.php file entirely. This will prevent text editors that introduce blank lines or excess spacing from breaking bits of the site by doing so. Since this file is pure PHP, the closing tag is optional anyway, and leaving it off ensures that the PHP interpreter does not produce output from it.
Reference this as well:
http://framework.zend.com/manual/en/coding-standard.php-file-formatting.html
Patch to remove config file closing marker