Transposh - Breaking language barriers

The transposh.org wordpress plugin showcase and support site

Version 1.0.9.5 – Fighting the code rot

by 10 Comments

After 16 years of operation and more than two years without a new release, our plugin encountered a widespread challenge known as code rot. This issue arises when functionality degrades over time—even without changes to the plugin’s code—due to external factors. New WordPress releases, updated PHP versions, and shifts in translation services can disrupt carefully designed features.

In version 1.0.9.5, we’ve tackled these challenges, with a primary focus on the translation engines. We removed outdated code and introduced new implementations to restore support for Yandex and Baidu translation services, which had stopped working in recent years. These updates ensure that the translation features are fully operational once again. Additionally, we’ve expanded language support to include new languages added to these translation services over time.

This release reflects our dedication to keeping the plugin reliable and effective, adapting to the evolving landscape of technologies and services.

We’ve introduced a new widget that utilizes standard flag emojis, which have been incorporated into the emoji set over the years. This update simplifies the widget’s code significantly, while also enabling easy customization of the flags to meet your specific needs.

You can check out this new widget in action on our site, where we’ve added a clever CSS trick that makes the current language icon twice as large as the others, achieved with just the following two lines of code!
.transposh_flags{font-size:22px}
.tr_active{font-size:44px; float:left}

We hope you enjoy this new version!

Version 1.0.9.3 – Fixing a bug

by 22 Comments

The newest releases focused on fixing reported security issues. However – one of the fixes used was to access some parameters using the filter_input function instead of accessing $_SERVER directly, this in turn made the previous version hit a 15 years old php bug which makes this not work as expected on some php platforms, mainly php-cgid. This version should fix this for effected parties who could not move up from 1.0.8 to 1.0.9.
Enjoy this new version

Version 1.0.9.2 – Moved development to github

by Leave a Comment

Some fixes and some code changes as usual, moved the development site from the old and spam ridden trac, and from the know it all wordpress to github. And this will allow our users to see the ongoing development of Tranposh. And maybe join us… who knows?

Take a look at https://github.com/oferwald/transposh/

I want to thank Amedeo Valoroso for helping locating the translate all bug, and encouraging me to update the plugin links.

Enjoy this release!

Happy new year – 2021

by 7 Comments

Well, this has been a busy year for me personally. I was unable to release new versions of Transposh in the needed frequency, and changes that happened in the wordpress framework has caused parts of the plugin to malfunction.

I will be updating the plugin soon. As there are several issues that are currently bothering users that have upgraded to a more recent wordpress. The first being a deprecation of old jQuery functions, causing the lazy loader used by the plugin not to function properly. This will probably get fixed by either replacing the lazy loader or canceling this feature. The arguments are divided between the different approaches. When Transposh was conceived, loading a useless script of 100k seemed a bit much, but the internet has since progressed in speed. And I am not really sure if people even bother to optimize their sites any more. The lazy loaders for jQuery which support CSS files are also rather rare, and nothing new has been released for a few years.

The second major issue was the usage of jQueryUI as the dialog platform that the plugin relies on. jQueryUI development has also been extremely quiet for the last few years. And I was unable to find a suitable dialog alternative. The need to change approach completely or write some dialog component of my own is another very large task. I will probably just make it work again. But this quick-glue solution will have to change.

I want to thank everyone who has been supportive of the plugin and its development in the last decade. This is what makes me keep supporting the plugin.

See you with a new release that fixes most bugs soon. And I share the global hope that 2021 will be better than 2020.