#35118 closed defect (bug) (invalid)
WP Admin showing Blank page because of wp-config file
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 4.4 |
Component: | Bootstrap/Load | Keywords: | |
Focuses: | Cc: |
Description
WP Admin showing Blank page because of wp-config file not closed end of the file . Its showing one extra line at bottom of the file .
--> I removed that line and closed it with php tag '?>' its working fine
In every update wp-config and theme function.php showing extra line
wp-config.php
/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');
?>
Attachments (1)
Change History (5)
#1
@
9 years ago
Please remove empty lines on wp-config and theme function.php files in feature release updates
#2
@
9 years ago
- Resolution set to invalid
- Status changed from new to closed
Hi, and welcome to Trac.
I'm afraid this isn't a bug with core, as the wp-config.php file shouldn't have a closing PHP tag (it doesn't when it's generated by WordPress), and WordPress updates never touch this file.
It sounds like you might have a plugin or theme that is touching files and not doing so in a proper manner, you could make a post on our forums at https://wordpress.org/support/ to help you track down what is doing this if you'd like.
#3
@
9 years ago
- Component changed from General to Bootstrap/Load
Hi @mynamevenu24,
Closing tags at the end of a file are not required in PHP. Omitting them helps to prevent developer errors where whitespace is accidentally left after the closing ?>
tag (Warning: Cannot modify header information - headers already sent
), which is just as bad as being left before <?php
, but is more difficult to spot.
Closing tag was removed in [10252] for wp-config-sample.php
, and in [19712] for all other files.
wp-config file