qTranslate and NextGEN Custom Fields

Also using the short tags [:en] and [:pt] doesn’t work.

Hi alex
I’m not familiar with qTranslate. I will try find some time to run it on a test installation and see if I can understand the problem.

I’m getting a fatal error trying to install qTranslate to a clean SVN version of WordPress.
I will try again later, but there’s not much I can do if the plugin won’t even install ??

Hi Shauno, thanks for the reply.

I forgot to tell that the qTranslate plugin that is in www.ads-software.com only works with WordPress 3.4.1.
To work with the 3.4.2 version one must download the qTranslate development version from the author site in .

Thanks

Sorry the link didn′t show up.

It’s https://www.qianqin.de/qtranslate/download/

I got it installed, but I’m not sure how it is supposed to work. I don’t have the time to go through all the help docs, so can you give me an overview of how you are using NGG Custom fields, and qTranslate together, and what you are expecting to happen?

Hi Shauno. I think i got it.

Normally to make a multilingual site with qTranslate one must wrap the content we write in special tags eg:

<!–:en–>English text<!–:–>
<!–:pt–>Texto Portugues<!–:–>

Then the plugin only shows the content language based on the browser language.

This works great with almost all plugins i have except NextGen Gallery, and now with NextGEN custom fields.
I think the problem is with NextGEN because from what i have read it doesn′t play well with qTranslate.

After a lot of reading i figured out:

Instead of:
<?php echo nggcf_get_gallery_field($gallery->ID, "Custom Field Name"); ?>

one must change it to:

<?php echo __(html_entity_decode(nggcf_get_gallery_field($gallery->ID, "Custom Field Name"), ENT_NOQUOTES)); ?>

I′m not a PHP pro so i don′t fully understand this code but it works.

Thanks

Hey Alex
What that code you pasted does is wrap the custom field value in WordPress’ translation function, which it seems is needed by qTranslate.
I’m glad you found a solution.