![]() |
After installing this a lot of sleeping mysql processes are appearing waiting up to 40 seconds and lot of network connections to google 500-1500 are reported when checking via netstat.
Switching on/off the cache brings nothing. Optimising mysql configuration - changing buffer sizes etc also dosn't help Allowing apache to keep the connection longer alive also brings nothing. Seems it is simply the problem of waiting for google to translate the sent text, that could take a while and why so many sleeping processes and permanent connections to google server. I think this could be escaped if one can have his own translator engine. Do you now if there is a one that one can install on his own server and provide online translation? |
To all vBET users.
Please note that vBET forum (http://www.vbenterprisetranslator.com/) is down at this moment. We are during vBulletin upgrade from 3.8 to 4.1.5 and we have some difficulties (like: https://www.vbulletin.com/forum/show...17#post2190817) We cannot tell how long it will take before vBET forum will be online again. It is big update, but hope it will be very fast and withour future accidents like actual one :) |
With all support questios please go to vBET forum: http://www.vbenterprisetranslator.com/
Just after we finish our upgrade of course ;) (see previous post) |
Hi :)
We just moved vBET forum from vBulletin 3.x to vBulletin 4.x It took much more time that we thought it will, because we got some issues with vBulletin. In fact we are still configuring some things, but at this moment we can open the forum again :) So sorry it took so long, and hope you will enjoy new forum :) |
Quote:
Quote:
:confused: |
Google api v1 will be closed by 1 December 2011, therefore free versions of vBET - 2.3.x/2.4.x will stop working after this time
Right now google api v1 sets its new, more strict, limits, so if You see blank page, there are some translations missing, You have probably reached your requests/translation limits. Furtheremore it is not vBET bug/error, if you face this problem please read this :FAQ Full version of vBET supports Google API v2(paid) and till march free translations provided by Microsoft translation API ! For anu questions, please visit our site: http://www.vbenterprisetranslator.com |
According to the google website
officially deprecated on May 26, 2011; it will be shut off completely on December 1, 2011 http://code.google.com/apis/language...reference.html The courtesy limit for existing Translate API v2 projects created prior to August 24, 2011 will be reduced to zero on Dec 1, 2011. In addition, the number of requests your application can make per http://code.google.com/apis/language...tarted.htmlday will be limited. For website translations, Its basically a case of uninstalling the mod unless you intend to pay google $20 per 2m characters being translated with the paid version of this I dread to think what the resulting google penalty will be with all the 404's you get until all pages are deindexed |
Agreed, dead MOD. RIP.
|
Indeed free versions of vBET can be considered dead, because Google Translation API v1 which is used by free vBET will be closed December 1st 2011.
We are really sorry to close free vBET version. We would like to still provide free translations services, but this is not up to us. vBET uses 3rd party translators and Google Translation API v1 will be paid soon. At this moment we do not know free translations API which will stay this way, so we are not able to switch provider in free vBET version. There is no sense to use paid translator provider in free vBET version - free is not optimized. We hope that some free translation provider will be available on the market (we are still looking for other possibilities) and we will be able to reopen free vBET version again. At this moment Full vBET version supports already Google Translation API v1, Google Translation API v2 (paid) and Microsoft Translation API (free till March 2012). Full vBET version will be still available and developed. Indeed free versions of vBET can be considered dead, because Google Translation API v1 which is used by free vBET will be closed December 1st 2011. We are really sorry to close free vBET version. We would like to still provide free translations services, but this is not up to us. vBET uses 3rd party translators and Google Translation API v1 will be paid soon. At this moment we do not know free translations API which will stay this way, so we are not able to switch provider in free vBET version. There is no sense to use paid translator provider in free vBET version - free is not optimized. We hope that some free translation provider will be available on the market (we are still looking for other possibilities) and we will be able to reopen free vBET version again. At this moment Full vBET version supports already Google Translation API v1, Google Translation API v2 (paid) and Microsoft Translation API (free till March 2012). Full vBET version will be still available and developed. |
Free versions of vBET reopened!!!
FREE translations are available again! Paid Google API is changed to FREE Yandex translation API. It supports less language pairs, but gives 1 000 000 FREE characters/DAY to translate. To compare Google gives 0 and Microsoft only 2M/month. Of course all 53 languages - each to each are still supported in full PRO version. |
All times are GMT. The time now is 07:26 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:
|