[wp-meta] [Making WordPress.org] #6835: Corrupt code in official documentation
Making WordPress.org
noreply at wordpress.org
Sun Mar 5 13:05:07 UTC 2023
#6835: Corrupt code in official documentation
---------------------------+--------------------
Reporter: Ov3rfly | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone:
Component: Developer Hub | Keywords:
---------------------------+--------------------
Code in official documentation at wordpress.org is corrupt.
Example: https://wordpress.org/documentation/article/htaccess/
This is confusing when it is necessary to point people with corrupt/lost
`.htaccess` files to an official source where they can compare and learn
the correct content.
Currently shown:
{{{
# BEGIN WordPress
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress
}}}
Expected:
{{{
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
}}}
In addition to confusion, the missing `<IfModule>` lines can also cause
fatal error 500 when code is copied to servers without `mod_rewrite` in
place.
The issue affects all examples on this page and has been reported already
a few times during last years via feedback at end of that page, nothing
happened.
Maybe a second issue: Is this feedback read by anybody?
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/6835>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list