FAQ

[r.dziadusz]

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 and Google Api Translation v1 have their own limits, in case of Google Api Translation v2 you can set it by your own) and since versions 4.4.3 and 3.3.8 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

[r.dziadusz]

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

[vBET]

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]

To add a flag to a mobile style, you need import vBET template:
1. Open AdminCP->Styles & Templates->Style Manager->Default Style->Edit templates->vbenterprisetranslator_flags.
2. Change value Style from Default Style to your mobile style.
3. Save the template.
If you want to add other vBET template (e.g. add a flag to translated messages) then import other needed vbenterprisetranslator styles.