For the first translation of some page to some language you have to be very patient. A lot of things to translate by google... And It is not possible to skip this time - it have to be translated. But after that having this page translated again to this language if very fast, because google isn?t asked for that anymore - just taken from DB.
Give it a chance and just wait till page is translated.
how long are we to wait for the site to be translated? a few hours went by and nothing happend so far.
I know that first question can look silly, but have to be sure - no other ideas
- Are you sure you check PHP version on server where script is intalled?
- Are you sure php was properly installed? In PHP 5+ MySQL is not enabled by default (In order to have these functions available, you must compile PHP with MySQL support - http://us3.php.net/manual/en/mysql.requirements.php) If not here you have PHP installation instructions: http://us3.php.net/manual/en/mysql.installation.php
how long are we to wait for the site to be translated? a few hours went by and nothing happend so far.
Definitively not that long 30 seconds, maybe 1minute if there is lot of text or lot of short words (i.e. tag cloud). On my forum I sometimes have such behavior that it translates, and translates, and... And after reload it is already translated. I assume that those are some browser sever issues because of long download time, and after reload it is already cached and goes fast.
So if reload gives you also nothing and you see that number of rows in cache tables is same - definitively it's something wrong. Need more info to be able to say what... some error logs?
nlp - only 2 tables are doing "something" on 1 of the sites. the medium and short tables are writing something in there. the cache isnt writing anything....what could be causing the cache not to write?
nlp - only 2 tables are doing "something" on 1 of the sites. the medium and short tables are writing something in there. the cache isnt writing anything....what could be causing the cache not to write?
those tables are to separate short, medium and long translations. Most forums have lot of short translations, then some medium and sometimes long. So it is ok.
I just wrote my own spider which goes to every page generated by vbSEO sitemap generator (must done little change in their code to automatically add all translations to sitemap) and also add rest languages available in google (over 40).
Now I have in sitemap 56 000 addresses. Spider will work for long time, and I will give you all some image about DB cache size.
Right now it just started only 100 pages done (not counting those which was clicked by users or other spiders), but it will already give you some proportions (keep in mind that I have over 40 languages not 28).
So it is ok that your wt_cache don't have to mutch data.
Also you can heck does wt_cache was appropriately created during installation. You need MySQL 5.0.3 or higher to be able to have it works, because I used varchar(65000) and in previous mysql versions varchar could have max size 255. If you have lower version - you can still use it. Just change VARCHAR(65000) to TEXT for column oryginalText drop table and create again from changed code.
When I finish my spidering I will made some automatic performance tests. Also change some other solutions (different indexes sizes, other order of filtering in SQL WHERE clause...). So it is possible that it will be even faster
Also good news is that when my spider makes translations all the time it doesn't affects speed of normal site generation (all lags are because of google translation server). So you can be calm - even if you wait long time for translation other users don’t feel it at all being on forum
those tables are to separate short, medium and long translations. Most forums have lot of short translations, then some medium and sometimes long. So it is ok.
I just wrote my own spider which goes to every page generated by vbSEO sitemap generator (must done little change in their code to automatically add all translations to sitemap) and also add rest languages available in google (over 40).
Now I have in sitemap 56 000 addresses. Spider will work for long time, and I will give you all some image about DB cache size.
Right now it just started only 100 pages done (not counting those which was clicked by users or other spiders), but it will already give you some proportions (keep in mind that I have over 40 languages not 28).
So it is ok that your wt_cache don't have to mutch data.
Also you can heck does wt_cache was appropriately created during installation. You need MySQL 5.0.3 or higher to be able to have it works, because I used varchar(65000) and in previous mysql versions varchar could have max size 255. If you have lower version - you can still use it. Just change VARCHAR(65000) to TEXT for column oryginalText drop table and create again from changed code.
When I finish my spidering I will made some automatic performance tests. Also change some other solutions (different indexes sizes, other order of filtering in SQL WHERE clause...). So it is possible that it will be even faster
Also good news is that when my spider makes translations all the time it doesn't affects speed of normal site generation (all lags are because of google translation server). So you can be calm - even if you wait long time for translation other users don’t feel it at all being on forum
I just use Googlebot lol, I have 500,000 total entrys after 24hrs.
Also no slow down at all, pages still fast as usual. DB size is 100MB so far.
Well I am still getting the database errors I quoted from the previous version, however the database is being populated and I actually finally got a page to show up in another language.
I will let this run for a bit now and see if I get more translated pages. Great job with this mod