![]() |
Are we saying the mod is not workable in any shape or form?
|
Quote:
If your website has appeal to people who's primary language isn't English, I reckon you'd be mad not to give it a go. Most of the people how have posted in this thread seem to be happy to share information or help each other. |
Quote:
Here is the reason why: Google Sitemap Update Frequency and Sitemap Stats Proper site maps make a huge difference when indexing :D |
Quote:
I was never discuss number of queries with you :) Keep focused! Or you don't have to because you are debug php/sql software for a living :D You still didn't tell do you even know what kind of queries are in this mod. Can you show me which query is such slow for you and what is the time of that query? Or just debugging php/sql software for a living you don't have to identify the problem? :D Are you able to point at least 1 slow query o master of masters who debug php/sql for a living? Thanks for laugh which you gave me :D :up: |
Quote:
|
Quote:
Here is my other suggestions / recommendation for the future:
Modify vBSEO sitemap to change the way they have suggested indexing the flags:
Code:
index.html Code:
index.html Code:
index.html The reason for this is that it is easier to manage the (long term) indexing process if the language links are all nice and neat in a few sequencial sitemap files v. interwoven around each link. (The "interwoven process" in a nightmare, quite frankly). Sorry, but the solution offered by the vBSEO team, while better than nothing, is not very manageable for large boards if you care about the convergence of Googles index with your sitemap. (Everyone should care if they care about SEO). We track this on a weekly basis and have currently have nearly 92% convergence. Google does not keep dumping and recrawling, etc. (as it currently happening with the translated links) because there is no update frequency associated with the hl=foo links :erm: Cheers. |
Quote:
Yes, it adds a lot of time (slow queries) when a page is first translated; but after it is translated (and snug-as-a-bug-in-a-rug in the dB), it adds less than 100ms to a showthread query. Naturally, since it must go across the network to sing the Google translation API song, that query will be very slow. It's OK to beat up on these guys, since the code is free and you don't seem to understand it yet. ;-) They are used to it, but don't expect flowery replies when you beat them up ;) I think they have done an outstanding job, and have donated one, of perhaps many, donations to these unsung heros of increased web traffic :-) In addition, I nominated this the "MOTM"! It is an amazing mod, and hopefully, will get better over time, if folks don't beat up the coders and chase them away! |
Quote:
|
Quote:
As you just wrote when page is first time translated long translation time is caused by http queries (requests) to Google for translation, not by SQL queries to DB (which are instant) :) We are not able to make Google faster ;) |
Also - thanks again for donation ;) :up:
|
All times are GMT. The time now is 01:57 PM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|