We’re ready with a new version of NextGen Gallery, with updated WPML support. This version will let you manage your galleries and maintain full translation using WPML’s String Translation module.
To translate your gallery, make sure that the String Translation module is enabled.
Translating strings in NextGen Gallery
All the gallery strings are under context ‘plugin_ngg‘. Don’t confuse this with the ‘plugin nextgen-gallery’ strings. The later ones are for translation of strings in NGG’s PHP, not in your galleries.
The string names will tell you what you’re translating. For example, gal_2_title is the title of gallery 2. pic_6_alttext is the ALT tag for picture 6. You probably get the idea…
The image and gallery texts will show according to the language of the page it’s been inserted to. You can insert the same gallery to pages in different languages and you’ll see different texts. The images remain the same.
We put together a small working example here:
http://subsite1.wpml.org/fr/french-album/
You can play with it and see how the gallery texts update when you change language.
What next?
We think that this round covers everything. The author of NGG is waiting for our OK to include these changes in NGG code.
Please help us test. When you tell us that it’s OK for you, we’ll pass the update on to NGG author and it will become part of the code for good.
Subscribe via RSS
Follow
Works like a charm! Brilliant
I have an Android app, NggManager that lets users manage a a nextgen gallery from an android phone using the wordpress xml interface. Are you adding xml functions to detect if the gallery is a multilingual gallery, and if so add titles and descriptions in the different languages?
The Android app shouldn’t care much about WPML. You will create the images normally. Then, go to WPML->String Translation and translate there. The gallery will display with the correct texts per language, according to the language of the page you insert it to.
There’s something I don’t understand. Why is the NextGen Gallery not translatable with the use of the language switcher at the top of the WordPress admin page?
My clients are really not savvy enough to use the string translation module to translate their new uploaded gallery and images.
So, out of curiosity; why isn’t the translation of NextGen working the way ‘it should be’?
It’s pretty difficult to say what’s not working for you this way. I suggest that you start a thread in our support forum. Explain what you’re doing and what you’re seeing.
You can follow the steps in this post and explain where you’re seeing anything different from this description. But, please use the forum for technical help, so that our support staff can assist you.
I have been planning a migrate my 1000s of photos to NextGen Gallery. A full integration with WPML would heavily weigh the decision in favor.
However, I note that in the article above, you essentially mention translating gallery names via string translation.
Will I be able to translate photo names/descriptions/tags as well? Will I have to that via string translation as well? If I have to translate photo properties via string translation, that would be a big pain in the backside….
Please can you help me understand? Thanks!
You can translate all the texts that belong to a gallery. The example talked just about the gallery name, but it applies to everything else. All the image tags are translatable now.
Hi, there is a problem with WPML with normal WPML and NGG. The slideshow widget contains, in nggfunctions.php the string:
‘domain: “‘ . trailingslashit ( home_url() ) . ‘”,’ .
this causes that widget don’t display in different languages because recall the wrong home page url (the language parameters added to the domain name).
Can you please post about it in our forum? Brooks from support wrote this and he can help fix whatever bugs are there.