Major Additions - TfSEO 2: the free vBulletin url rewrite

TfSEO 2.1

TfSEO is a powerful and free url rewrite for the vBulletin system: it rewrite forum, thread and post urls.
For me it's very hard to explain well all the feature of this plugin, soo the best way is test it.

How much does it weight on the server?

I have tested on my home server:

TfSEO enabled, heavy:

[root@hserver ~]# ab -n 100  http://hserver/tfseo_1/main-forum-f2/dsadas-t4
This is ApacheBench, Version 2.0.40-dev <$Revision: 1.146 $> apache-2.0
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Copyright 2006 The Apache Software Foundation, http://www.apache.org/

Benchmarking hserver (be patient).....done


Server Software:        Apache/2.2.3
Server Hostname:        hserver
Server Port:            80

Document Path:          /tfseo_1/main-forum-f2/dsadas-t4
Document Length:        33804 bytes

Concurrency Level:      1
Time taken for tests:   22.177687 seconds
Complete requests:      100
Failed requests:        0
Write errors:           0
Total transferred:      3420400 bytes
HTML transferred:       3380400 bytes
Requests per second:    4.51 [#/sec] (mean)
Time per request:       221.777 [ms] (mean)
Time per request:       221.777 [ms] (mean, across all concurrent requests)
Transfer rate:          150.60 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    0   0.0      0       0
Processing:   220  221   0.7    221     223
Waiting:      209  210   0.8    210     213
Total:        220  221   0.7    221     223

Percentage of the requests served within a certain time (ms)
  50%    221
  66%    221
  75%    222
  80%    222
  90%    222
  95%    222
  98%    223
  99%    223
 100%    223 (longest request)

TfSEO disabled, standart vburl:

[root@hserver ~]# ab -n 100  http://hserver/tfseo_1/showthread.php?p=4#post4
This is ApacheBench, Version 2.0.40-dev <$Revision: 1.146 $> apache-2.0
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Copyright 2006 The Apache Software Foundation, http://www.apache.org/

Benchmarking hserver (be patient).....done


Server Software:        Apache/2.2.3
Server Hostname:        hserver
Server Port:            80

Document Path:          /tfseo_1/showthread.php?p=4#post4
Document Length:        34010 bytes

Concurrency Level:      1
Time taken for tests:   21.870820 seconds
Complete requests:      100
Failed requests:        0
Write errors:           0
Total transferred:      3441000 bytes
HTML transferred:       3401000 bytes
Requests per second:    4.57 [#/sec] (mean)
Time per request:       218.708 [ms] (mean)
Time per request:       218.708 [ms] (mean, across all concurrent requests)
Transfer rate:          153.63 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    0   0.0      0       0
Processing:   216  218   0.9    218     220
Waiting:      205  207   0.9    208     209
Total:        216  218   0.9    218     220
WARNING: The median and mean for the waiting time are not within a normal deviat                                                                                                 ion
        These results are probably not that reliable.

Percentage of the requests served within a certain time (ms)
  50%    218
  66%    218
  75%    219
  80%    219
  90%    219
  95%    219
  98%    220
  99%    220
 100%    220 (longest request)

Like you can see product takes about +10ms per request.

Live Demos

1. Light
2. Medium
3. Heavy

AdminCP Demo:

For Support and question you can contact me at davide {at} techforum .it

This product will be updatefor long time, I welcome (and really do ask for) any feedback, suggestions, issues, etc...

If you install it, click install.

Note: vbulletin will have by default a rewrite system from version 4.0 (beta should coming next month, april). I relly suggest you to wait, and not use this product. If the vb's rewrite will be great, i will no more update this product.

[superjeff]

PS: Plugin now use both your "function remove_accents" and unhtmlspecialchars, to be sure

[koxito]

Question:

Lets suposse i install this.. ? does this affect all the link to the threads that look like this ?:

http://www.xxmysite.com/forum/showthread.php=12421352 ... couse a lot of the users links their threads in the signatures and stuff, and i dont want them to change all the links in the forum.

[superjeff]

Old links will automatic redirect to the new one:

You can see, to example im my forum:
http://www.techforum.it/showthread.php?t=858 is automatic redirect (with a 301) to
http://www.techforum.it/f47/tfseo-un...bulletin-t858/

Soo no problem!

[Magnumutz]

Dude... i think it would be better if you'd code it in English... so it would be easier for other users to customize or improve it. Cuz not that many of us know italian.

[superjeff]

You have right, but i don't know english very well, so i preferred to code this product in my lenguage. With an update i can traslate in in english.

[nfn]

Developing in English is a good practice an you can get more help.
My primary language isn't English too ... it's Portuguese!

[jscieza]

Erm... how about this URL?
http://www.techforum.it/f46/connette...t-con-un-t780/

Compare the title of the thread and the rewrited URL, it seems to be slightly different :S

[jack bro]

I think it is because it only puts the first few words from the title of the thread into the URL so if you have a thread which is titled with 50 words, the URL won't be massive.

Jack.

[nfn]

I think is not using the last version because he is "eating" accents. You can define the number of words in the url.
Does Google penalize long urls?

[superjeff]

Originally Posted by jack bro

I think it is because it only puts the first few words from the title of the thread into the URL so if you have a thread which is titled with 50 words, the URL won't be massive.

Jack.

It is true. I don't have much time, and the link structure in my forum is a bit different.

Originally Posted by nfn

Does Google penalize long urls?

Usually, no. But have you ever see a very long url in a Google's serp? It's very bad. Google eat the url and write something like "yoursite.com/...". I think this is bad to see, and you could be penalize from the user that "jamp" your result.