FAQ

[Marcin Kalak]

If everything was working well and suddenly it not then one possibility is that you have issue with your translation provider (others are: some configuration was changed, new mod added, some software updated).


To check this, upload the appropriate file from the package vBET do-not-upload/tools/providers-tests/. In this directory contains files for testing providers translations.

Example test for googleapiv2:

1. Upload file test_googleapiv2.php to /core/admincp.
2. Open a browser page:

   YourForumAddress/admincp/test_googleapiv2.php

3. If everything is ok you will get answer:
   

   Starting transaltion test
   Test result: {"responseData": {"translatedText":"Welcom"}, "responseDetails": null, "responseStatus": 200}
   Test error:

In case of error check that you have the correct API key in Admin CP -> vBET -> Translation Providers.

[Marcin Kalak]

Is that the server timed out and closed the connection.
Set variable wait_timeout for mysql server to higher value.

Here you can find a full solution:
MySQL server gone away error explained

[Marcin Kalak]

If you have in your URL:

caracter%C3%ADstica

Probably you use IE browser. IE browser bad shows url with the accented.
Try to check this link in another browser (Opera, Firefox),
should be translated correctly.
This is a browser issue. google crawls this link correctly (with the accented).

[Marcin Kalak]

So to support other translation APIs jut go to Admin CP -> vBET -> Translation Providers and turn off option Use Google ONLY. This is only step which is necessary to support other translation APIs

After that vBET will use other translation API always when it is possible. So if some translation is supported only by Google, then Google will be used, BUT if other supported API is able to do the translation then by default ALWAYS will be chosen other provider than Google.

You are also able to determine which exactly provider should be used for specific language pair (From-To). And you are able to do this for each possible language pair. So if you want to have full control and determine yourself which translation engine should be used for language pair, then you can do it by configuration files from directory vbet_translation_options. Each file includes language code at the end of name and this determines 'From'. To determine 'To' you have to open the file and change appropriate line in php table.

For example. If you want to set translation from English to Polish to be done by Microsoft Translation API. Then:
1. Open file /vbet_translation_options/vbenterprisetranslator_from_en.php
2. Find line with Polish language code mapping and set name of chosen translator:

'pl'=>'Microsoft',

So this sets Microsoft Translation API as translation provider for translations made 'From' English (en), 'To' Polish (pl). Piece of cake
Of course this will work only when option Use Google ONLY is disabled. This is just example - please remember that you do NOT have to do this. By default it is already set to not use Google whenever it is possible.

Also please keep in mind that some translation APIs can require to set some identification parameter. All such parameters, with detailed description you will find in options group Admin CP -> vBET -> Translation Providers

NOTE:Everywhere where language pair is supported by more than one provider, you will see comma separated values with providers names. For example:

'pl'=>'Microsoft,Google',

It means that as long as Microsoft is available vBET will use Microsoft and if it is not available then vBET will automatically switch to Google. In such case vBET marks provider as unavailable and checks every hour (by scheduled task) is it available now. If yes, then vBET will switch back to preferred provider.
You are able to change order in providers queue or remove some provider at all from there. Please note that you cannot use spaces between values.

This way vBET will be able to provide translations even after limits in one provider are reach.

Also in case when all providers are unavailable vBET will use dummy translator which simply displays original text. So in such case you can see not translated text on translated pages. It is better strategy that displaying empty texts and something must be displayed. Please note that such results will not be cached, so test will switch to translated as soon as any translation provider will be available again.

[Marcin Kalak]

1. Add to vBET ignored pages as many content as you think is not important for translations
Example of some pages which can be considered not important for translation by some forum owners: member pages, calendar, photo galleries.

2. Use free translation services first
Use first free version of translations API: Microsoft, Apertium -than turn on paid Google API v2

3. Limit supported languages to those which you think are most important for your forum. And even then limit it more - after time you can add more languages if you find that costs are OK for you. Add new ones from time to time when your cache is full
We provide support for 53 languages but for some forum smaller amount is better, also you can cache your data as long as you want, so you can add new languages one after another, without reaching your limits!

4. Do not clear your database cache and disable automatic cleaning
Remember to improve value of cache ttl or even disable it(0) - you can find it here: admincp -> vBET Cache -> Database Cache ->Cache Time To Live (TTL)

5. Avoid translation of SPAM, by verifying posts until those are published.
Not translating, unwanted information will reduce your number of translations!

6. Look for other translation services which Terms Of Service allows to add it into vBET and let us know about those - will gladly support as many translation APIs as possible
We are seeking for new free translation providers, help us and help yourself, make us know about new translation providers! Now vBET is created in way to support many providers, therefore if terms of use let us implement it, we will do it!

7. Reduce your amount of request per second (Only for Google translations API v2)
You have to change and increase this , but remeber to big value will slow down your forum dramticaly: admincp -> vbet -> translation options -> Delay between

8. If you are using Google API v2, set your own limits
You can set your own limits, and control your translation costs! Just go: https://code.google.com/apis/console/b/0/ -> Quotas

9. Turn on option Don't translate numbers.
Enabling this option will reduce the cost of translations, because will be made less translations.

[Marcin Kalak]

If you see untranslated text it is not vBET bug or error. It appears when you've reached your limits in all tranlation APIs - you can easly check it here:

AdminCP -> vBET -> Translation Providers Availability

NOTE:
It is strongly unrecommended to change these values manualy, becouse vBET will do it itself!

In this situation (there is no available translation API) vBET will use dummy translator. It means that already cached translations will be displayed and for not existing translations original text will be shown (not empty one like before - this can happen only when provider refuses translation).

Translation providers set limits (Microsft Api Translation have their own limits, in case of Google Api Translation v2 you can set it by your own) and vBET when more than one provider supports translation then vBET will use preferred one first.

And in case if one of translation API is not available - which means you have reached your limits - vBET will switch to another, and in every 10 minutes vBET will check is the translation API available again.

Please note that you have to turn off option Use Google Only and set appropriate API keys to use providers queue. For details please see:

Admin CP -> vBET -> Translation Providers

Also You can check if you reach your limits by run these tests TESTS

[Marcin Kalak]

Part translation is caused by reaching your limits, but it not an error!

Simply i.e.:
1. Someone wrote message and it was translated because you didn't reach your limits - limits are set by translation providers(in Google Api Translation v2 you can set it by your own).

2. When next message was written, limits was reached and translation providers unavailable therefore you will see on your page already cached translations text from cache and original content, for next message, because translation services were not available.

3. After any translation provider is available again, untranslated, original message will be translated. vBET checks translation API availability in every 10 minutes

[Marcin Kalak]

Basically it is enough to turn on Guest Cache (Admin CP -> vBET Cache -> Guest Cache -> Use Full File Cache For Guests).

When Guest Cache is on, then showing translated URL's under the flags is enabled. For performance reasons it works only for guests. It is not necessary for logged in users to see translated URL's under the flags - such user mostly is already on translated page before log in, or do not need translation at all. The feature is mostly for search engines spiders which are crawling any existing link on page. So now Google will not complain about lot of redirects.
And because showing translated URL's under the flags it is integrated with Guest Cache it will not give any performance penalties, since additional queries to database will be made very rare (only when refreshing cache).

Please note that there can be several situations when URL under the flag is not translated and redirection still happens:

• Always for logged in users (as described before it is not necessary to waist resources)
• When URL is not translated yet (for performance reasons do not ask for all flags translations immediately, but after first redirect translation will be available in database cache)
• When URL is translated already, but also page is already cached in Guest Cache with no translation (this is related to previous point, but as soon as Guest Cache expires your guests will see translated URLs under those flags which are already translated)

So assuming: it is working for guests only, with delayed requests for translation - for performance reasons.

[Marcin Kalak]

At the beginning of the .htaccess file you must have a rule:

RewriteEngine On
Options FollowSymLinks

If you use the links to SEO, you should add a rule for SEO links: http://www.vbenterprisetranslator.co...html#post15127

At the end of the file you must have a rule:

RewriteCond %{QUERY_STRING} !redirected=
RewriteCond %{QUERY_STRING} !do=
RewriteCond %{REQUEST_URI} !(core|admincp|modcp|clientscript|cpstyles|images|css|js|login|auth|ajax|install)
RewriteRule ^(.*)$ vbenterprisetranslator_front_controller.php?redirected=$1 [L,QSA]

You can find these rules into your download files:

do-not-upload\tools\redirecting-rules\

[Marcin Kalak]

If you upgrade vB5 and vBET stopped working then make sure that you have the appropriate rules in .htaccess (http://www.vbenterprisetranslator.co...html#post15140). vB5 during update overwrites the .htaccess file and you must to add again our rules to it.