#12594 closed defect (bug) (fixed)
Use paths in include calls
| Reported by: | nacin | Owned by: | sorich87 |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.0 |
| Component: | Performance | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
We often do require('admin.php') where require('./admin.php') would be quicker, as it would avoid the include_path directive.
We should audit core for instances where we include a file (it'd generally be a bootstrap) without specifying a relative or absolute path.
Attachments (1)
Change History (10)
#3
@
16 years ago
- Resolution fixed
- Status closed → reopened
Testing patches is a good idea. This completely breaks trunk.
Warning: require_once(./class-oembed.php) [function.require-once]: failed to open stream: No such file or directory in [...]\wp-includes\media.php on line 1358 Fatal error: require_once() [function.require]: Failed opening required './class-oembed.php' (include_path='.;C:\php5\pear') in [...]\wp-includes\media.php on line 1358
#5
@
16 years ago
- Keywords needs-patch added; has-patch removed
- Priority normal → highest omg bbq
- Severity normal → blocker
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
I added a relative path where no path is specified