I want to thank Dave for writing such a cool package, and for putting up with me. My ISP "did something" to make it work, and I am thrilled. Dave bent over backwards trying to help me get it together.
To those who are removing the ad, just remember karma is a Bit..
Is the language you pick supposed to be "sticky"? While I am getting the translations fine, when you click a link of the forum page rather then seeing page two in the language you picked, you are seeing it in English. Is this the way it is supposed to be or have I still got some work to do?
Is the language you pick supposed to be "sticky"? While I am getting the translations fine, when you click a link of the forum page rather then seeing page two in the language you picked, you are seeing it in English. Is this the way it is supposed to be or have I still got some work to do?
I noticed that as well, it doesn't get stickied. Only on the page that you are on. That in itself is a pro and con though I think.
Amazing Mod! Is it possible to add other languages? If yes what is simplest approach to it... i would like to have Brazilian and a few other in the list... how could i do it? Thanks again!!
while we have some information as to how much traffic is increased, what about the real traffic that matters which is converting this to more membership.
Can anyone correlate this increase in traffic to getting more members?
while we have some information as to how much traffic is increased, what about the real traffic that matters which is converting this to more membership.
Can anyone correlate this increase in traffic to getting more members?
I think the stated goal of this mod is to increase search engine referral traffic. Converting new visits to members (active or not) is a completely different process. Any "stats" in this area would be misleading, IMHO.
Thats ok. Cleaner ans saver are only for maintenance - those are used manually when you want to delete duplicated data wrom wt_cache once a while. such duplication can happen only in this table - possible, but rare
I have a related question.
Would it be more efficient and faster to have database tables for each translation instead of "small" and "medium" mega tables for an entire site?
We have been running this mod for just a few days, and at the current tables growth rate, our translation database will be nearly 1.2 Terrabytes in three dB tables when it is all "done and dusted" as they say, hahaha. I calculate this, perhaps incorrectly, as it seems Google has have cached around 200 pages (for each of 28 languages =~ 6000 pages) out out nearly 400Kpages, and the translation dB is currently 600MB. If we assume approximate linear growth, the full transation dB would be 400K/200 * 600 MB or 1.2 TB
I notice that our translated pages are much slower loading than the same page not in the translation dB (by quite a large factor, much slower, even though there are less MySQL queries for the translated page).
Why not put the translated pages, at least, in their own tables?
while we have some information as to how much traffic is increased, what about the real traffic that matters which is converting this to more membership.
Can anyone correlate this increase in traffic to getting more members?
For me it's not relevant. My forum is in Polish and I don't want anyone who doesn't know Polish be user.
Would it be more efficient and faster to have database tables for each translation instead of "small" and "medium" mega tables for an entire site?
We have been running this mod for just a few days, and at the current tables growth rate, our translation database will be nearly 1.2 Terrabytes in three dB tables when it is all "done and dusted" as they say, hahaha. I calculate this, perhaps incorrectly, as it seems Google has have cached around 200 pages (for each of 28 languages =~ 6000 pages) out out nearly 400Kpages, and the translation dB is currently 600MB. If we assume approximate linear growth, the full transation dB would be 400K/200 * 600 MB or 1.2 TB
I notice that our translated pages are much slower loading than the same page not in the translation dB (by quite a large factor, much slower, even though there are less MySQL queries for the translated page).
Why not put the translated pages, at least, in their own tables?
It wouldn't DB has set indexes and data access is instant and constant
Translated pages will ALWAYS generate slower that not translated because first is generated normal page and after that it's translated
vB Global Translator - Multiply your indexed pages & put search traffic on autopilot Details »»
About Developer
Uses Plugins 
No support by the author.
07-17-2009, 01:40 PM
DB has set indexes and data access is instant and constant 
