#12594 closed defect (bug) (fixed)
Use paths in include calls
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 3.0 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Performance | Keywords: | |
Focuses: | Cc: |
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)
#1
@
15 years ago
- Keywords has-patch added; needs-patch removed
- Owner set to sorich87
- Status changed from new to accepted
#3
@
15 years ago
- Resolution fixed deleted
- Status changed from closed to 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
@
15 years ago
- Keywords needs-patch added; has-patch removed
- Priority changed from normal to highest omg bbq
- Severity changed from normal to blocker
Note: See
TracTickets for help on using
tickets.
I added a relative path where no path is specified