Posts Tagged release

Version 0.9.3 – Where did my flags go?

They didn’t go very far, please watch this video or read the instructions below.

What should you do to get them back?

Just upgrade to the full version using the following instructions:

  • Upgrade to the latest version from wordpress.org (which will be the last, there)
  • Check “allow upgrade to full version” in the settings
  • Check for upgrades and perform the upgrade, that’s all!

What’s new in version 0.9.3:

  • Update will work from our site
  • Some bug fixes
  • Ability to remove the rel=alternate which was not always useful
  • (0.9.3.1) We have released a sub version to incorporate the new languages supported by Google, making our total count – 73! (If anyone here speaks Hmong, please contact us)

We hope you’ll enjoy this version.

 

 

, , , ,

39 Comments

Version 0.9.2 – 4 years and we don’t break

Lovely tulips

We grew 4 (actually 5) tulips for our anniversary

Yes, it was over four years since the first version of Transposh for wordpress was released. And indeed, we have come a very long way.

Transposh is being used by thousands of sites all over the web, and we have many happy users (and a few less happy ones :) ).

This version, 0.9.2, is not really what we expected to have by now, after four years we would have expected that a version one (maybe even two) will already have been released. But apparently, life does rarely proceed as you plan it to.

The title of this posts actually refers to a new behaviour of our parser, when we used to encounter an   (which should be a non-breaking space) we actually broke the phrase into two, which is rather the exact opposite of what things should have been. So hopefully this is now fixed, and we’ll no longer break!

Other changes include:

  • Basic support for Woocommerce integration
  • Override the case when other plugins or themes cause the process_page to be called prematurely
  • Fix a nasty bug when the same translation appeared in a paragraph more than once
  • Bing have added two languages
  • Fix the bug reported by dserber disallowing language selection on post where translate_on_publish was disabled
  • Update for .po files, Turkish Translation by Ömer Faruk Karabulut

You will enjoy this version! This is an order! :)

, , , ,

3 Comments

Version 0.9.1 – Improving constantly

Translation Bring People Together

Translation Bring People Together

Should have posted earlier about 0.9.1 which is a rather nice version with some nice improvements. But we have waited for this extremely nice animation, made on Fiverr by an amazing animator, that happens to be related by blood to the team here :)

We have also created a nice Widget Gallery page, just go and see!

Other changes include:

  • Added some help inside the Admin interface for very common questions (keys – no, you don’t need keys by default)
  • Allow jQueryUI version to be overriden, resolving many conflicts (old themes, all sort of components with unsorted versions of jQuery and jQueryUI)
  • A fix when some bad plugins insert .css in an inappropriate way (this disabled the ability to see which languages were selecred)
  • Added the transposh_echo function – see our development site for documentation and usage
  • Fixes for widgets, easier inclusion with shortcodes, old dropbox fixes, ids removed
  • Adding touch punch to admin, allowing language selection on touch devices
  • Fixes for minor issues discovered since 0.9.0

What are you waiting for? Download the latest version now!

 

 

,

4 Comments

Version 0.9.0 – Ready, settings, go!

On the 12/12/12 (what a lovely date) at 20:12 (an appropriate time). We have released version 0.9.0 of our plugin. This version included a major rewrite of our settings and administration page. Moving from the single very long page with oh so many options to a slick tabbed interface.
This version is not only cosmetic but it also included two major features enabled by the settings new advanced tab:
1. Inclusion of debugging support: Now we will be able to give you better support using the plugin ability to create logs, and allow remote debugging.
2. Advanced parsing rules: This feature allows you to change the way texts are being broken for translation on your site. It allows a much finer granulation and fitting the engine to your specific use case.

However – be warned, those features, although well tested are marked advanced and experimental. Use them only if you understand what you are doing.

There are so many other features and bug fixes included, that many of them deserve their own post, but for now, lets go over the change log:
* A new language selection widget based on select2 (Very nice select box with flags)
* Added ctrl keys for quick navigation of previous/next blocks (Improves speed of working with the interface)
* A new option that allows to reset the configuration file to the recommanded defaults
* Css fixes for twenty twelve theme
* Avoid loading the subwidgets in the admin pages
* Removed distinction between editable and viewable languages, now a language can only be active or disabled
* Updating jQueriUI to 1.9.2 (jQuery should now be 1.6+)
* Fixes the z-index for the old style dropdown (patch by chemaz)
* Fixes the bug with the coupling of Chinese simple and traditional
* Fix bug preventing upgrade from very old versions
* Suppress notices when widgets are created directly with our function
* Avoid rewriting urls in the default language, mainly effected canonicals
* Our script is needed when the widget allows setting of default language
* Finally solved the problem with MSN translate and CR/LF

In the days following the initial release, three bugs have been uncovered and fixed, if something simple is not working, make sure to refresh your files.

Enjoy this version!

, , , , ,

9 Comments

Version 0.8.5 – We support Lao too

A frog and a mouse welcome Laos

Well, Google just announced on their translate blog that they will support Lao, the official language of Laos, so we have added the code required and did a quick release with support to this language, which is also supported by One Hour Translation.

The version is already out for a few days but the real problem with getting this post live was finding a picture. We are not quite sure it is the most appropriate picture, but at least it rhymes.

Enjoy this new version.

, , ,

No Comments

Version 0.8.4 – Professional human translation is here

Professional work

Professional work

Less professional work

Less professional work

We are very proud to present this release of our plugin.

This version, in addition to normal enhancements and bug fixes, finally integrates professional human translation with a basic integration with OneHourTranslation.com professional translation service.


The way this works is the following:

  • Go to OneHourTranslaion.com and create an account
  • Use the account details generated and insert them to Transposh’s settings page
  • When using the translation interface, an admin (and only an admin) will see a “One Hour Translation queue” button
  • Pressing this button will add the phrase to a queue, another click will dequeue the item
  • 10 minutes after the last phrase was added a translation project will be generated on one hour translation
  • Give it an hour (or less from our experience) and the translations will appear on your site
  • Everybody is happy and you actually support the Transposh project (Yay!)

This is rather new, so if Murphy strikes, just contact us and we’ll do whatever we can to make things work.

Now, for the rest of this release:

  • Fixed flag of Swahili to Tanzania as noted by Ed Jordan
  • Lots of fixes to backup service
  • Fix for a parser bug when having translate in default language following a select element
  • Fixed XSS reported by Infern0_ (big thanks!)
  • For programmers: Added a global function to return the current language “transposh_get_current_language()
  • Seems like Lybia has a new flag too ;)
  • Fixed widget IDs containing a backslash so that we’ll pass w3c validation
  • Updated jQueryUI to 1.8.23 to avoid conflict with jQuery 1.8 used by some themes
  • Portuguese (Brazil) translation by Amilton Junior

Our operators are waiting for your feedback, if you get a busy signal, try contacting us again!

P.S. This is the very first version to have passed 1,000 daily downloads, we are humbled.

, , , ,

6 Comments

Version 0.8.3 – The widget’s shortcode

This version fixes some bugs and adds support for a nice shortcode that allows you to place the widget inside the post

For example, this:
[tp widget="flags/tpw_flags_css.php"]

Will display:

, ,

11 Comments

Version 0.8.2 – 3 years, 66 languages, 1 wordpress

I said 3 candles on that cake!

It has been three years (and three days, and thirty three hours) since the first version of Transposh plugin has been aired on the wordpress.org plugin repository.

Time surely flies.

This has been the first leap year (29th February) and a real leap year for Transposh. The plugin has been downloaded from the repository over 50,000 times this year and has made a steady growth of features and total number of languages supported. And today with the addition of Hmong Daw we are the first plugin to support a total number of 66 languages.

This was a really interesting (as in, have an interesting life) year for the automatic translation industry and plugins, where Google has nearly dropped their API support (only to switch to a pay model) while Bing imposed new limits. Transposh has successfully overcame those changes, while other plugins did not survive.

What does the future holds for Transposh? We are slowly boiling some new stuff, working on our vision to improve website translation, when things will be ready – they will be out. Meanwhile, your continued support is important to us, sometimes a simple email with “your plugin is great” drives us to continue. So if you believe we are doing well, drop us a line, if you think we should improve things, drop us a note, and if you think that we suck, we fail to understand why you have read this message up to this point ;)

Wishing ourselves a great 4th year, maybe it will end with a bigger cake :)

 

, , , , ,

21 Comments

Version 0.8.1 – It’s not a bug! it’s a feature!

Hunting bugs with advanced technology

At Transposh we pride ourselves in our high coding standards, this means that we have no bugs in our software. Yes, you have heard this right, zero bugs found. However – there is a slight problem, other people are not like us and they actually do have bugs in their codes. So if you installed Transposh and something is not working correctly, there is probably a bug in WordPress, or a bug in the theme you are you using, or a conflict with another plugin, or jQuery made some mess, or you are still using Internet Explorer 2 or this is something related to your mother, or her mother, or her grandmother, or the first cell that was ever created. It is never us! never ever!

If something is not working and you report it to us, we immediately find someone else to blame, and sometimes, when in good mood, we actually code something to avoid those other people bugs.

This release is one of those releases, the only new feature is the ability to set comment languages in the management interface (if someone posted in Spanish while actually browsing your site in English or vice verse) .

The rest of this release is:

  • Enable live human translations backup by default
  • Lists of languages used in Javascript are fixed and more readable
  • Improved loading for backend javascripts
  • Support the , symbol in parsing (Its not a comma, really!)
  • Reintroduce CORS support in our AJAX (Cross Origin Ajax)
  • Try to make sure lazyloader loads in the correct context
  • Fix calculation of batch translation size to avoid translations too large for Google
  • Fix when two jQueryUI versions are included, mainly for wordpress 3.2.x
  • Fixed widget to remove [Language] which was buggy as noted by Philip Trauring
  • Fix broken sites for users using the widget function directly
We hope you’ll enjoy this version

, ,

46 Comments

Version 0.8.0 – Attack of the APIs

When APIs fight

Well ahead of the deadline posed by Google Translate API to stop working, we were finally able to compile this new release. This one followed a long period of problems that were presented by the older version, mainly because of the fact that Google decided to pose limitations on usage before their deadline which caused the previous versions support requests to surge to new heights. The Google change also triggered an API limit in the Bing translation API, since users were switching engines, which overloaded the Transposh hard coded API key for Bing.

However, we survived this period to provide you with our latest and greatest version. This version fixes these problems be providing a bypass (Proxy for Google and temp keys for MSN) and it also allows you to use your own key directly (thanks to Randy from spyware help center for providing us with his key for testing) which will take precedence over those other methods. While doing this we were able to dramatically improve the infrastructure of the plugin, changing the way AJAX calls were performed to a method that is native to WordPress (e.g. if your admin page works, it should probably work as well). While doing that we were able to reduce javascript code needed for the backend while allowing the translate all feature to work much faster (and supporting Apertium too!).

At this point we had a solid version, which seemed like a good thing to release, but no, we had to have some other features in, so we finally decided to tackle the issue of multiple widgets support (and title selection too, yippee!). Seems quite straight forward? but no, this caused a major rewrite of our widget infrastructure as well. Actually improving it quite drastically with changing the way css was added, and the way the widgets notified the servers of change in language (we now avoid a useless POST call to the server). While writing that we were lucky enough to stumble upon a PHP5.3 to PHP5.2 incompatibility issue with a set of other problems which held our release back another week. We want to thank the many users that have put up with our beta releases and helped us find problems that were hidden under layers of code and complexity.

We also took this opportunity to change our terms slightly, if you are displaying Google ads from AdSense on your translated pages, we will take 1/1000 of that space for use with our own adsense code, so if Transposh is helping you generate a revenue of $10K you will be buying us coffee! So thanks! To clarify things a bit, we don’t create additional ad space on your page, and we won’t insert any ads or change your layout, if you have no ads, we do nothing. If you think that this is asking too much, you may simply delete our plugin, whistle a soft tune, and be on your way. If you want a commercial license, we don’t sell them yet, but they’ll probably cost more.

Other changes to this version include:

  • Added Catalan and Hindi support for Bing – speaks for itself.
  • Dropdown widget improved css – it actually looks much better now.
  • Support for Memcached – if APC and other opcode caches were too much for you, now you may use memcached and have a lot of fun.
  • Better 404 page handling (don’t create new links to non-existing pages) – meaning the google crawler will hassle your site less.
  • Fix caching on rackspace cloudsites – they had x-cache installed for opcode cache, but with no user memory, which caused a surge in logfiles – now fixed.
  • Many more minor fixes – We might count those, but we don’t have enough fingers.
  • Turkish Translation by Semih Yeşilyurt.

We hope you’ll enjoy this version, and as always, waiting for your comments, ideas, suggestions and flames.

P.S – Tested on WordPress 3.3 beta4, works great.

, , , , , ,

65 Comments