Version 0.9.0 – Promptus, occasus, ire!

Sc 12/12/12 (quid desiderabilem date) ad 20:12 (congruum tempus). Lorem released version 0.9.0 nostri plugin. Hac versione includitur a major RESCRIBO nostri occasus et administrationis page. Moving ex uno longissima page with oh tot bene ut lubricum tabbed interface.
Is poema poematis est non solum medicamine sed includitur etiam duo major features enabled per occasus novum proficiebat tab:
1. Inclusione debugging sustentationem: Nunc te melius poteris sustinere posse facere per ligna plugin, et permitte remota debugging.
2. Provectus parsing regulas: Is pluma sino vos ut mutare viam textus sunt rumpi pro translatione in vestri site. Quod sinit multo tenuiores granulation et aptare machinam vestris specifica usum casu.

Tamen – admonendi, vultus, quamvis bene temptatae sunt praenotati proficiebat et experimentalis. Quid agas, si uti scies.

Tam multi sunt, alius features et bug fixes includitur, quia multi ex eis dignus sua propria stipes, Pro nunc, lets perambulare mutatio log:
* A novae linguae Selectionem widget substructio in select2 (Valde nice selectis arca archa cum flaccescit)
* Added accidit claves velox navigationem superiorum / postero Stipitibus (Amplio celeritas operari cum interface)
* Novum option quod sinit reset configuratio file ad recommanded defaltis
* Css fixes pro viginti duodecim themate
* Vitare onerantium subwidgets in admin pages
* Submotus distinctio inter editable et viewable linguarum, nunc linguam potest esse nisi activa vel disabled
* Adaequationis jQueriUI ad 1.9.2 (jQuery iam agi 1.6+)
* Fixes z-index propter antiquam style tellus (patch a chemaz)
* Fixes cimex cum conjunctione Chinese simplex et traditional
* Fige bug prævenientes upgrade ex vetustissimis versions
* Supprimere notices quando widgets creata sunt directe cum nostris functio
* Vitare rescribo URLs in defectu lingua, maxime fit canonicals
* Nostri script opus est, cum widget admittit occasusque default lingua
* Postremo solvitur forsit per MSN Perfruere vita et CR / LF

Diebus post primam solutionem, tres bugs fuerint discoopertis et obfirmaverat, si aliquid simplex dicitur non operabatur, planto certus ut refoveo vestri files.

Sidi version!

, , , , ,

  1. #1 by Tim in January 9, 2013 - 6:34 PM


    First of all I would like to appreciate your incredible work, good job !!!

    I am struggling to use transposh with new bing translator setup which has now new approach of using client ID and clientsecret key .

    In transposh it ask for single bing API , however I was expecting 2 fields for each cliendID and ClientSecret

    I may be wrong in approach but my study so far has lead me to this conclusionSeek your help and guidance if possible.
    Thak you for reading my issue :-)

    • #2 by offer in January 11, 2013 - 12:28 in


      I agree with the contents of your comments, but I’ll tell you what the situation is and why I am not doing anything about it
      1. The current key free solution works nicely
      2. The old key works for anyone who has such a key
      3. The new key requires a new method of interacting with a temp key (10 minutes life) which is rather annoying

      Sic, if I’ll fix it, I will have to do tons of work and testing, while harming users with current keys.

      When will I do this? Probably only if the first solution starts to fail miserably, or I find myself with too much spare time (not very likely :) )

      I hope this helps (or at least explains it)

      • #3 by Tim in January 11, 2013 - 2:43 PM

        Gratias ago pro auxiliis vestris,… :)

  2. #4 by Marty in January 22, 2013 - 1:30 in

    Ofer, thanks for your work on this plugin.
    As usual with the updates, there is a need to go into parse.php and change some of the settings. This time no matter how I change the settings for punctuation breaks and number breaks, my previous translations for the whole site are lost. I know they’re not lost, just suddenly no longer visible. What has happened to parser and how can I get my translated phrases to load again?

    • #5 by offer in January 22, 2013 - 1:32 in

      Hello Marty,

      Those changes in parser.php got migrated to the advanced tab in the settings, so you won’t have to do that manually any more :)


  3. #6 by Marty in January 22, 2013 - 1:47 in

    OOOH, I SEE. It’s now on the WordPress side! Fixed. Love it!!!! Lorem, Ofer.

  4. #7 by Dasep in January 27, 2013 - 1:35 in

    hello ofer.

    i would like to thank you very much for your transposh. it made any website or blog easier to rolling the world, even they are newbie just like me. i have apply the transposh 0.9.0 plugins in my sidebar widget, and it’s work.

    sed, i need something more from you, placet. just for your info, my home page is statics without sidebar of course. :D that’s why, my visitor can not choose their language directly. i think i need a short code. can you give me please?


    • #8 by offer in January 27, 2013 - 1:39 in


      You could look at the FAQ and find code your can include in your theme,

      There are also shortcodes, you can read all about them on our development site at:


  5. #9 by Angelus in February 13, 2013 - 7:44 PM

    I suggest to add the compatibility with the search engine o the wordpres. Now we can only search in the default languaje

(non lacus)

Current vos @ r *