Well, This version fixes some issues. Does not fix others (Yes, anonymous translation is enabled by default, if you wish – turn it off, it is your call, not a security problem). Also, an editor *SHOULD* be able to see which people created translations before him in the translation log. This is not an “information disclosure” but rather a feature, very similar to your ability to see who wrote a post on your site. If you don’t want it, just don’t allow anyone other than admin to translate and you are “safe”.
This version also fixes the XML sitemap issue, since they have upgraded a minor version (4.1.4 to 4.1.5) yet changed everything internally (mixed case to camel case, not too important, but still, a breaking change).
Another important thing, I will no longer be using wordpress.org, I honestly believe that I don’t work for them. I really don’t trust and confide in them, and this is final. New releases will be here, if the plugin update mechanism works on your site you will be able to upgrade. I will also soon remove the .1 ending from versions, since there will only be one version.
If you have anything to say to me, please use the contact form here, I will probably answer in due time. Commenting on those posts also work.
Good luck and have fun using this version.
Version 1.0.8 – Thanks Julien!
On this special palindromic date, a new version of Transposh is released. This version was held back for way too long but since I finally got the time, it is up and available.
So, what good is it for?
First, I would like to thank Julien Ahrens from RCE Security for his help in detecting of several weaknesses in the previous version, and working with me on providing fixes and validating them. Julien provided me with the information and full disclosure and was very patient with me until I finally had the time to fix everything. I can only give him my highest recommendation, and show my appreciation here. THANKS!
Other things in this version include a fix for the notorious regression with Google Translate, causing people to get [object window] and/or duplicate content. If you are using Google Translate, please use the new button in the utilities tab in order to delete duplicate data. Saving an up to date backup of your human translations is always a good idea.
There are also tons of improvements to the misleading tab called translation editor (which, in hindsight I should have probably called “translation management”) which allows you to have better control and visibility of current translations.
Lots of work here was dedicated to compatibility with PHP8 and wordpress 5.9, I believe that most problems were eliminated, and the widgets should work in the interface again, I want to thank all the users that helped me with testing this, and especially Alex and Marcel. thanks guys!
The next version will hopefully come sooner, I think that I will take development and forums to github or a similar platform. Let me know if you have any thoughts on that.
Feel free to contact us or leave your feedbacks on this post, we thrive on your positive inputs and idea (and wither on the negative…) so do help us to provide you with one of the best and free translation tools available.
Language Switcher for Transposh plugin
This is a guest post from Marco Gasi of Codingfix. I appreciate his work and allowed him to use this space to tell you something that you might find interesting as I have. So without further ado, here is Marco’s post
As many other developers, when I discovered Transposh plugin I immediately fell in love with it! It allows automatic translations out of the box but it also gives you a granular control on the translated text, allowing you to edit every single phrase.
Okay, you already know that so it’s not necessary for me to repeat here why we all love Transposh so much.
But I have to confess something: I was not happy with the language switcher widget. I develop small websites and usually I need to use from 2 to 4 different languages. Building non-WordPress websites, I used to put just some flag in the main navigation menu and wished I could do the same using WordPress and Transposh.
The artisan way
At first, to get that result, I used a couple of useful plugins and just a bit of javascript.
I won’t waste your time here to talk about this: if you’re interested you can find a detailed description here
The WordPress way
The “artisan way” was absolutely boring to me: for each new website I had to repeat every step just to get 2 or 3 flags in my menu. I wanted to get my flags just installing a plugin and maybe adjusting some settings… But that plugin didn’t exist, so I finally decided I had to go beyond my limits, meet the challenge head-on and create my own plugin.
Today I’m proud to present Language Switcher for Transposh. It’s not magic, it doesn’t do miracles but it gets the job done.
I’m very grateful to Ofer, who invited me to present my little creature in his blog: thank you, Ofer, for your kindness, I really appreciate this opportunity to let Language Switcher for Transposh be known.
So, what Language Switcher for Transposh actually does?
- it reads Transposh settings and gets the list of languages used in the current website
- it reads all menu locations available in the current theme and allows you to choose where the language switcher will show up through simple checkboxes
- it allows you to add at the end of the chosen menu(s) a series of flags or a dropdown menu to select the language; Administrators, Authors and Editors will see an Edit translation button too which will allow them to activate the Transposh Translation Editor
- if you choose to use only flags, it allows you to choose between Transposh flags or flags provided by Language Switcher for Transposh itself
- if you choose to use a dropdown you can choose if using a select or an unordered list to build your dropdown: I added this option because unordered list give you much more options to customize their look and feel than a select
- if you use an unordered list as dropdown, you can choose if the list items will show flag only, text only or both flags and text
- it allows you set additional classes for your language switcher menu items: this allows you to make it look accordingly to your theme style using the same class your theme is using for navigation menu items
- it allows you to totally customize your language switcher using a css editor with syntax highlighting: current stylesheet is loaded in the editor and you can just modify it and then save it or you can even create a totally new css file. with a custom name (it defaults to custom.css)
What about the future?
I already have a TODO list to add more features and maybe to create even a premium version, but I think that Language Switcher for Transposh will make your life easier in this first release already. Or at least, this is what I very much hope!
You can find Language Switcher for Transposh in WordPress.org website (or just searching for “transposh” in the admin dashboard of your WordPress installation): give it a try and feel free to contact me for any issues you can get into. And obviously, if you like it, don’t forget to give it some star (I still didn’t learn how to put in the dashboard those annoying invitations to rating LOL).
Thank you all for reading.
Good coding!
Sincerely,
Marco Gasi by Codingfix
Version 1.0.7 – rolling again
Yup, this is February 2nd. Which is a good date as any to make a new minor release. This version should work out of the box with WP 5.6 (and probably 5.7 too). And includes some minor fixes for bugs encountered in the last year.
I wanted to thank Fabio Perri for his help with testing this release and for not giving up on Transposh. I guess he will find more bugs soon and a new release will follow.
Next version will probably include some more versions released by bing translator as well as removing of some old and unused code.
We hope you will enjoy this version.
Happy new year – 2021
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.
- « Previous Page
- 1
- 2
- 3
- 4
- …
- 21
- Next Page »