Hello
As we promised we give you support for other translations APIs! As now vBET supports not only Google but also Microsoft Translation API!
This version is considered BETA, because of big changes to support other translation APIs, but previous version vBET4.3.0 is now considered stable. In vBET4.4.0 there was only 3 little bugs corrected from previous version, also some changes made for vBulletin4.1.4 new editor. All details below.
NOTE: there is one additional update step necessary:
- Upload to server content of directory upload-once from vBET package (includes configuration for multi translation API support)
BUGS corrected:
- Translate vBSEO message (vBET 4.2.1 does not translate vBSEO Javascript messages)
- Removing not translated area comments (Does not strip away the no-translate tag for TITLE, default language)
- Keywords with special characters
Changes for vBulletin 4.1.4 new editor:
- Wrap new CMS article comment in lang bbcode for vB4.1.4 (vBET and ckeditor in 4.1.4)
- Editor content translation on translated page for message preview and going from quick to advanced editor (vBET and ckeditor in 4.1.4)
- Redirect for ckeditor.php requests on translated pages (vBET and ckeditor in 4.1.4)
Known issues (we consider it as vBulletin bugs and wait for vBulletin response for official bug reports):
- Online users issue (quick fix: http://www.vbenterprisetranslator.co....html#post8985) (vBulletin bug report: vBulletin JIRA)
- New blog entry for other language issue (vBulletin bug report: vBulletin JIRA)
And as always - Enjoy vBET!![]()



2Likes
LinkBack URL
About LinkBacks
Reply With Quote
