vBET 4.4.5 and 3.5.3 Released

[vBET]

Hi

Today we have for you new releases for booth vBET 3.x and 4.x. Most important changes:
- New free translation API is supported (Apertium)
- Added support for Microsoft Translation API by Azure (paid one or free with 2milllions/month character limit)

Please note that you have to configure API key to use new APIs - see description of parameters in Admin CP -> vBET -> Translation Providers.

For all release details please see below.

NEW:

• Apertium Translation API support
  It supports only some language pairs and is slower than other APIs but it is free. It is best to use it with also other API which has support for all to all language pairs (Microsoft for 35 languages or Google for 53). Even if you are still using free Microsoft it is good to use Apertium too - you will have bigger limits.
• Microsoft Translation API by Azure support
  You can still use free Microsoft Translation API until end of March 2012 - it will be closed then. After that date you can use Microsoft Translation API by Azure. You can create there paid account or FREE one - yes Microsoft will be still free with limit 2 millions characters per month.

Changes:

• Change in setting providers availability for vBulletin 3.6
• SMALL license changes to describe Apertium as one of translation providers
• Default value of TTL for guest cache is 1 day now
• Removed support for Google Translation API v1 (it is closed by Google now)

Bugs corrected:

• Class 'vB_Template_Runtime' not found (http://www.vbenterprisetranslator.co...rrors-php.html)
• Call to undefined function vbet_doRedirect() (http://www.vbenterprisetranslator.co...rrors-php.html)

[ctrenks]

Thank you so much for getting a free API involved to at least fil the blanks!

[vBET]

Thank you so much for getting a free API involved to at least fil the blanks!

We will add more when we find it

[legalhelp]

Is this a free version? Where can we download it?

[r.dziadusz]

This is full comercial version of vBET, you can buy it here

[r.dziadusz]

Hi,
Now, when we are aware of some "not-translating" issues, and in order to keep up with latest change in translation APIs, we have to make some additional changes in code.
Here are quickfixs for them:
Apertium translation API code update
Google v2 translation API code update

All this changes will be implemented in vBET next realeses for both versions

[mario06]

Do I have to do this fix myself, you have access to my ftp?

[r.dziadusz]

Please note that issues are discussed and being solved in specyfic thread