.htaccess - Revision history

Akers at 02:51, June 14, 2011

2011-06-14T02:51:57Z

Akers at 02:51, June 14, 2011

2011-06-14T02:51:47Z

Dustin at 16:43, June 15, 2010

2010-06-15T16:43:51Z

Dustin: Created page with 'The .htaccess file is a plain text file containing rules for rewriting URLs. For example if a user browses to http://yoursite.com/test/ this may be rewritten to internally send …'

2010-06-02T16:01:44Z

Created page with 'The .htaccess file is a plain text file containing rules for rewriting URLs. For example if a user browses to http://yoursite.com/test/ this may be rewritten to internally send …'

New page

The .htaccess file is a plain text file containing rules for rewriting URLs. For example if a user browses to http://yoursite.com/test/ this may be rewritten to internally send the user to http://yoursite.com/index.php?page=test without them seeing this. This is an easy way to have better looking URLs that run one script or piece of software. WordPress uses rewrites to allow for standard or custom permalinks.

== Example standard .htaccess file ==
<pre>
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
</pre>

== Line by line breakdown ==

<pre>
# BEGIN WordPress
</pre>
* This is a comment informing WordPress' internals where its rewrites begin.
<pre>
<IfModule mod_rewrite.c>
</pre>
* This informs the web server to only parse the following lines if rewrites are available.
<pre>
RewriteEngine On
</pre>
* Enable rewrites.
<pre>
RewriteBase /
</pre>
* Base URL for rewriting. If WordPress is in a subdirectory named 'subdirectory' then this should be: RewriteBase /subdirectory/
<pre>
RewriteCond %{REQUEST_FILENAME} !-f
</pre>
* This is used for permalink parsing and may vary.
<pre>
RewriteCond %{REQUEST_FILENAME} !-d
</pre>
* This is used for permalink parsing and may vary.
<pre>
RewriteRule . /index.php [L]
</pre>
* This is the destination that rewritten URLs are directed to. If WordPress is in a subdirectory named 'subdirectory' then this should be: RewriteRule . /subdirectory/index.php [L]
<pre>
</IfModule>
</pre>
* End lines that only parse if rewrites are available.
<pre>
# END WordPress
</pre>
* This is a comment informing WordPress' internals where its rewrites end.

@@ Line 9: / Line 9: @@
 # Click the ''Save'' button. This will generate a new .htaccess file.
 # Verify that your problem is now fixed.
 == Example standard .htaccess file ==

← Older revision		Revision as of 16:43, June 15, 2010
Line 52:		Line 52:
	</pre>		</pre>
	* This is a comment informing WordPress' internals where its rewrites end.		* This is a comment informing WordPress' internals where its rewrites end.
		+
		+	[[Category:PluginBuddy]]

@@ Line 1: / Line 1: @@
 The .htaccess file is a plain text file containing rules for rewriting URLs.  For example if a user browses to http://yoursite.com/test/ this may be rewritten to internally send the user to http://yoursite.com/index.php?page=test without them seeing this.  This is an easy way to have better looking URLs that run one script or piece of software.  WordPress uses rewrites to allow for standard or custom permalinks.
 == Example standard .htaccess file ==
@@ Line 13: / Line 22: @@
 # END WordPress
 </pre>
 == Line by line breakdown ==