Can you try something along these lines and report back the result? <?php if(qtrans_getLanguage()==’en’): ?> // attachment if statement <?php else if(qtrans_getLanguage()==’fr’): ?> // attachment if statement <?php endif; ?> Technically you could omit the second else if statement and replace it just with <?php else : ?> assuming you only have two languages you … Read more
Maby you should use the wp_editor instead? Then you have more control of the editor. An example if you have a meta box called “myfield” in the custom post type. If you want a simple editor you can do like this: echo ‘<form action=”” method=”post” target=”_blank”>’; wp_editor(‘<p>Some content</p>’, ‘myfield’ ); echo ‘<input type=”submit” value=”Submit” /></form>’; … Read more
I figured it out. For the reference problem was links in custom post types. As it appears Qtranslate in its current iteration doesn’t support custom post types. And the_permalink or get_permalink will not change to current lang as you switch them. Solution was very simple. Just include this in functions.php file of your theme. add_filter(‘post_type_link’, … Read more
This doesn’t have much to do with Genesis, other than you need to hook into the header in one of several ways, with Simple Hooks http://wordpress.org/plugins/genesis-simple-hooks/ or in functions.php. I’ll leave that to you. But using <?php echo qtrans_getLanguage(); ?> do something like this: $currentLang = qtrans_getLanguage(); if($currentLang == ‘fr’) { //show french logo $imageName … Read more
Use WordPress i18n functions. Normally good plugins are translation-ready, and you should create your translation files for that plugins (if not already present). Explain how to is too much for this answer, start looking at Codex page linked above, search Google and also have a look here. If a plugin is not translation-ready use another … Read more
I have written a function that will convert the qtranslate-x string into array of language and based on that you can use a particular language. /** * This function breaks q-translate string into array per language. * * @param – {string}$content – the q-translate string Eg : [:en]Title in English[:fr]Title in French * @return {array/bool} … Read more
You can try like adding content in this format in Widget title/text content. [:en]My English Title[:fr]My French Title and on echoing this.. q-translate will make them work .
I’m afraid it would be very hard to do. qTranslate stores all titles in one database field as concatenated string with some additional markup, so there is no chance to sort them using SQL and to do it fast. You can do one of 2 things: 1. Stop using qTranslate It really has many other … Read more
I’ve found a solution and described it here: http://shtrak.eu/vloo/tech/language-is-already-enabled-or-invalid-when-enablin-new-language-to-qtranslate/ Watch out for older database converters that might wipe out your content!
i have added keywords of my plugin to hi_IN.po file and generated .mo file. Finally i found text what i added is in hindi language. and in my plugin i displayed those texts with the help of function __(). ex:- __(“Read More”)