Version 0.6.0 – Going from fast to faster

Image by Nathan Eal Photography
was fast but now faster

This version is a major release, and there is lots of new stuff in this release. so lets get over the list of items

  • Now there is support for auto batch translations which makes translations faster and improves user experience, previously Transposh has to load scripts from the various auto translation backends and then it would iterate on the phrases one by one to get translations, now those are grouped together for reducing the numbers of requests made, the fact that no external scripts are loading reduces complexity and improves speed.
  • MSN (bing) translator does no longer require a key, as they have upgrades their API and switched to using an application key, you can now just select the default translation engine at will, if this engine is not available for that language – Transposh will resort to using the other one.
  • Transposh Google Proxy is now included to enable translation for Alpha level languages from Google (with 5 new languages supported – Armenian, Azerbaijani, Basque, Georgian and Urdu) – this proxy is located inside the plugin and redirects requests to google translate from your server allowing the script to use them. This process is slow – it increases the load on your server – and is generally not very recommended, and will be eliminated as soon as Google releases those languages to general consumption. But if you have the urgent need to translate your site to the Azeri people, at least you can do that.
  • The Transposh logo and backlink can now be removed from the widget, if you choose this option – Transposh will attempt to make some money of existing ad space on your translated pages only, this money will help us in our development effort, if you don’t want to lose any money from your ads, just keep the link. The terms are readable here.
  • The translate all button was also revamped, and should be much faster using batching.

The usual share of bug fixes is here, and I would like to thank Rogelio and Marko for their insightful comments and contribution to fixing those bugs. An attempt was made at the plugin header error, but as we can’t reproduce it we don’t know if it works, so crossing our fingers. If this release is badly broken for you, please report this at the comments here, create tickets for us in our trac. Bug us on our twitter account or our facebook page or by calling our cell phones, preferably at 3 am. You can always revert to the previous version, we are not offended.

We hope you’ll enjoy this version.


  1. says


    I have suggested

    widget add reset button go defalut original laguage

    widget default title add h2 h3 selection


    best regards

    • says

      regarding the h2 h3, just use your css files to achieve that.
      and the reset button? since you have pluggable widgets, that would be a snap to code, just take any widget and change it appropriately

      thanks for the suggestions

  2. says

    I love this plugin. It just keeps getting better and better. The only problem I have with it at the moment is that I can only use it once. And because I have a static front page to my site, this means I have to choose between putting it on the front page or an inside page, and not both. That’s not good because I never know where a new user is going to land and the new user won’t know that he can translate a page if he can’t see the Transposh button right away. Is it possible that you can make the widget a multiple instance widget like some of the others?

    • says

      Hello Terence,

      First, the good news is that I have just committed a deeper buddypress integration to the svn, mainly it integrates with the activity feed much better.

      Scond, I use buddypress on a test site, using their default theme and I don’t have a similar issue, plus you can always add another widget instance with the code:

      < ?php if(function_exists("transposh_widget")) { transposh_widget(); }?>

      Good luck

Leave a Reply

Your email address will not be published. Required fields are marked *