Opened 5 years ago
Closed 5 years ago
#7685 closed defect (bug) (invalid)
No closing PHP tag in functions.wp-styles.php and functions.wp-scripts.php
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | lowest | Milestone: | |
| Component: | Optimization | Version: | |
| Severity: | minor | Keywords: | |
| Cc: |
Description
Is there a reason why the two files (functions.wp-styles.php and functions.wp-scripts.php) didn't contain a closing ?> for the PHP script ?
Change History (3)
- Milestone 2.7 deleted
- Resolution set to wontfix
- Status changed from new to closed
- Version 2.7 deleted
comment:2
jacobsantos — 5 years ago
- Resolution wontfix deleted
- Status changed from closed to reopened
Actually, the reason is that the two files, as well as two other files are part of BackPress and not of WordPress, which has the convention of including the closing PHP tag.
You may create a ticket at http://backpress.automattic.com/ and see what is said there.
This is actually invalid, since it isn't part of WordPress.
comment:3
jacobsantos — 5 years ago
- Resolution set to invalid
- Status changed from reopened to closed
Not part of WordPress. See BackPress.
Note: See
TracTickets for help on using
tickets.

No closing ?> tag is the preferred style in most web applications. This prevents accidental whitespace at the end of the file from being output prematurely (before headers and such are sent).
While it's not generally the style in WordPress, it is the recommended style by virtually all of the PHP community.