Opened 17 years ago
Closed 17 years ago
#8062 closed defect (bug) (fixed)
.htaccess Issues
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 2.7 | Priority: | normal |
| Severity: | major | Version: | |
| Component: | Permalinks | Keywords: | |
| Focuses: | Cc: |
Description
I just updated to the newest version in the trunk (9515). The whole site is now returning a 500 error. I traced this to the .htaccess file, which now reads:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase Array
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . Arrayindex.php [L]
</IfModule>
# END WordPress
I cleared the file, but when I tried to reset my permalinks, it reverted to the broken version.
Somewhere along the line, an array is being returned where a single variable is expected.
Change History (5)
#3
@
17 years ago
I was looking at an older version of rewrite.php.
The code causing the issue is
$home_root = parse_url(get_option('home'));
if ( isset( $home_root['path'] ) ) {
$home_root = trailingslashit($home_root['path']);
}
It looks like the if condition is false, causing the problem.
Note: See
TracTickets for help on using
tickets.
Tracing the issue a bit further, $home_root in /wp-includes/rewrite.php is the unexpected array.
$home_root = parse_url(get_option('home')); $home_root = trailingslashit($home_root['path']);Could this be related to a setting on my site or is it a bug in the code?