Motive: I am building my own simple cms. But when doing htaccess for my posts I am stuck when I want to add text after the id passing in url.
What i have tried so far is:
RewriteRule ^blog/(.+)$ post.php?id=$1
The problem is that when I type in http://example.com/blog/1 I get the post returned. but when I go to http://example.com/blog/1/hello-world its not working.
I want the text hello-world added to permalinks for SEO purpose.
In addition to writing regex in .htaccess, you could also route all of URLs to one PHP script, like Wordpress does:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
Then, inside index.php you can split $_SERVER['REQUEST_URI'] to parts and process as you wish, like this:
$parts = explode("/", $_SERVER['REQUEST_URI']);
if($parts[1]==="blog")
{
$id = intval($parts[2]);
include("post.php");
die();
}
Below RewriteRule working fine for me.
RewriteRule ^blog/([0-9]+)/(.*)?$ blog_detail.php?id=$1&title=$2 [L]
hello-world part in your example) is only relevant when you are creating the uri's (when you are constructing a link for instance)/blog/1/hello-world is a three-level url, while /blog/hello-world is a two-level url. Search engines consider a two-level url more important. And as you are checking the id AND the slug anyway, you don't really need the id (you probably do need it internally though, so don't remove the column from your database)Since your 'ugly' url does not use the title, you can simply match it, but ignore it. You are currently matching 1/hello-world in your first capture group, and your post.php page can obviously not handle this. Instead match the following:
RewriteRule ^blog/([^/]+)/[^/]+$ post.php?id=$1 [L]
Edit: Someone claims that this approach is inefficient. I beg to differ. You can do the following in php to redirect requests that were done using an incorrect url. It's exactly as efficient as a comparison of $_GET['title'] and $expectedtitle, then constructing the url. The difference is that you have no useless variables lying around, and the intention of this code is clear. You want to redirect the user if the url is not the expected url. That the expected title is not the actual title is a sideproduct.
$expectedtitle = getTitleById( $_GET['id'] );
$expectedurl = "{$_GET['id']}/{$expectedtitle}";
if( $_SERVER['REQUEST_URI'] != $expectedurl ) {
header( $expectedurl, TRUE, 301 );
}
/blog/1/hello-world and /blog/1/bye-world will both be matched and both return the same post, resulting in duplicate content... So you'll have to cross your fingers search engines will not find out about other possible url's
%{REQUEST_URI} as far as I am concerned.