[high]Copyright:[/high] You may use this modification at your own risk. I cannot and will not be held responsible for any damage you may cause to your forums during installation or thereafter. You may not distribute this modification in whole or parts and anyone found doing so faces risk of prosecution. All my modifications are released at vBulletin.org and anyone found releasing them elsewhere also faces risk of prosecution. You may not translate this modification without my prior permission.
[high]Donations:[/high] I release my modifications for free. If you wish to donate please contact me and I will give you my details. All donations are graciously appreciated.
What does this modification do?
This modification will allow you to automatically have more search engine friendly URLs in your vBulletin. A forum which would normally display as forumdisplay?f=1 will now appear as f1-forumtitle.html and the same with threads. Having keywords in your URL can be of an advantage in search-engine ranking.
Requirements:
You must have mod_rewrite apache module enabled on your server. Contact your host for more information.
This will not work well for non-english boards as it strips most non-alpha numeric characters. E.g. ? would be stripped on french boards etc
Installation
1/
Please read the readme.txt file included in the zip for details on how to install this modification.
Please Click Install!
If you installed this modifcation please click the install button. It'll help you keep up to date with future releases and important bugfixes, security updates.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
First, kudos to Dean C for working on this and enabling all those who wish to get away from an encoded schema (look at vbulletin... people will pay for commercial, but do you need to encode the product?).
Second, I've made my own modifications (as I said before) and I love it.
Thirdly, I have no issues with it. Browse around, check it out: http://de.castlecops.com/forum. Alls well in wonderland.
First, kudos to Dean C for working on this and enabling all those who wish to get away from an encoded schema (look at vbulletin... people will pay for commercial, but do you need to encode the product?).
Second, I've made my own modifications (as I said before) and I love it.
Thirdly, I have no issues with it. Browse around, check it out: http://de.castlecops.com/forum. Alls well in wonderland.
Kudos to CastleCops I refer all the people dumb enough to get spyware to you guys with a nice big HijackThis Log heh
Kudos to CastleCops I refer all the people dumb enough to get spyware to you guys with a nice big HijackThis Log heh
There can never be enough kudos flying around. Again, you're a testament to open coding and enabling vbulletin to go SEO for so many (including us). As to the malware stuff, we just released this today, hope it helps: http://castlecops.com/a6341-Malware_...Procedure.html.
Kafi: Please could you navigate to my website and send me an email through my contact form using your email. I'll send you a reply with the latest version I'm working on, which should fix the foreign chars issue
Kafi: Please could you navigate to my website and send me an email through my contact form using your email. I'll send you a reply with the latest version I'm working on, which should fix the foreign chars issue
Well I noticed on castlecops you still have the foreign chars in the actual URI's. My problem with that is that no-one showed me evidence that these chars are actually valid in a URI. I've changed a lot since then but I used this function to convert foreign chars to their english equivalent:
PHP Code:
// function to replace foreign chars with their english equivalent
function remove_accents($text)
{
$trans = get_html_translation_table(HTML_ENTITIES);
foreach($trans as $literal =>$entity)
{
if(ord($literal) >= 192)
{
$replace[] = substr($entity, 1, 1);
$search[] = $literal;
}
}
return str_replace($search, $replace, $text);
}
Well I noticed on castlecops you still have the foreign chars in the actual URI's. My problem with that is that no-one showed me evidence that these chars are actually valid in a URI. I've changed a lot since then but I used this function to convert foreign chars to their english equivalent:
PHP Code:
// function to replace foreign chars with their english equivalent
function remove_accents($text)
{
$trans = get_html_translation_table(HTML_ENTITIES);
foreach($trans as $literal =>$entity)
{
if(ord($literal) >= 192)
{
$replace[] = substr($entity, 1, 1);
$search[] = $literal;
}
}
return str_replace($search, $replace, $text);
}
You need to take a look at IRIs and the URI-> IRI mapping (international resource identifier).
You need to take a look at IRIs and the URI-> IRI mapping (international resource identifier).
After a quick browse around google and reading up, it seems as it's a work-in-progress and not yet fully implemented/supported in the development world?
DC SEO vB URL Rewrite Details »»
About Developer
Visit Web Site
Uses Plugins 
Is in Beta Stage 
11-12-2005, 12:49 PM
There can never be enough kudos flying around. Again, you're a testament to open coding and enabling vbulletin to go SEO for so many (including us). As to the malware stuff, we just released this today, hope it helps: http://castlecops.com/a6341-Malware_...Procedure.html.
