Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
  • #45933


    I’m using mqtranslate for my website.
    I have been able to translate all the content but I don’t know how to do so for
    the website subtitle
    the website footer
    the feature content of the homepage
    and the info written in the featured slider
    and is it possible to do so for the widget? I would like to get one widget title in both languages (French and English)

    here is the website: africpass.be

    Thanks in advance 🙂


    @Virgile: Sorry we are not expert in translation and you should ask in plugin support forum for that. We have no idea about that plugin. We have only worked with WPML translation plugin and they help us to make Catch Kathmandu Pro compatible with WPML. See this http://wpml.org/theme/catch-kathmandu-pro/


    Hi Sakin,

    thank you for your answer.
    Do you know if I must clear all my English content first and then write it again, if start to use WPML?

    Because actually I have found way to translate subtitle, featured content and widget titles by adding [:en]My English Title[:fr]My French Title.
    So I don’t want to start again from the beginning.

    The problem is I can’t still translate footer, featured slider on the homepage and homepage headline. Is it something related to the theme?


    @Virgile: If you find the way to translate and found that plugin is easy then yes sure use that plugin. I have also heard about that plugin.


    Hi Sakin,

    I am a bit confused with what you say here in this thread.

    I have just bought the Kathmandu Pro theme because in this website you say that the theme supports qTranslate (mqTranslate is a fork of qTranslate because the latter is no longer updated by his original developer).

    As Virgile says, the theme fails on supporting some elements in the homepage. In my case, I can’t display the proper language for subheadline and slider contents. I don’t have a translatable text in the footer but I have noticed problems there too, as Virgile pointed.

    I would really appreciate some help in managing this question. Thank you very much!



    I have some more information to add:

    In this thread:


    some time ago you said:

    I will add function to reset all the transit needed using the condition inside the functions like this:

    if ( function_exists( 'qtrans_convertURL' ) ) {
    	delete_transient( 'catcheverest_image_sliders' );

    In another post in the same thread you talk about theme support for qTranslate.


    I’ve been looking at the code of catchkatmandu-functions.php and most of the functions related to displaying info in the homepage do not have such a piece of code like that one above. In fact, at the very beginning of every function there is a commented call to delete_transient. I just uncommented the line in the functions that manage the items I needed to properly translate and now everything seems to work ok.

    So, can we conclude that some work is still needed in the theme code? Might it be a problem in any sense the fact of having uncommented those lines?

    Thank you very much again for your help!


    @Jaume: Are you using Catch Kathmandu Pro, then it should work fine. As we have added in all the delete cache as

    if ( ! function_exists( 'catchkathmandu_qtranslate_invalidcache' ) ) :
     * Template for Clearing qtranslate Invalid Cache
     * To override this in a child theme
     * simply create your own catchkathmandu_qtranslate_invalidcache(), and that function will be used instead.
     * @since Catch Kathmandu Pro 2.0
    function catchkathmandu_qtranslate_invalidcache() {
    	delete_transient( 'catchkathmandu_post_sliders' );
    	delete_transient( 'catchkathmandu_page_sliders' );
    	delete_transient( 'catchkathmandu_category_sliders' );
    	delete_transient( 'catchkathmandu_image_sliders' );
    	delete_transient( 'catchkathmandu_homepage_headline' );
    	delete_transient( 'catchkathmandu_homepage_featured_content' );
    	delete_transient( 'catchkathmandu_footer_content' );	
    	delete_transient( 'catchkathmandu_footercode' );
    	delete_transient( 'catchkathmandu_featured_image' );
    } // catchkathmandu_qtranslate_invalidcache
    add_action( 'after_setup_theme', 'catchkathmandu_qtranslate_invalidcache' );

    So, it should work fine. But if it’s still not working. Then contact me through email. I have emailed you.


    Hi Sakin,

    Thank you for you answer. I managed to make it work properly. Let me tell you what I have done, as you might probably update your theme the same way.

    qTranslate plugin is no longer maintained by its former developer, so somebody in the community forked it with the name mqTranslate. This is the plugin most people is using nowadays, as Virgile said in the first post of this thread. It is also my case.

    The (easy to solve) problem with Catch Kathmandu Pro theme (and probably with other Catch themes) is that in functions.php the existence of qTranslate plugin is validated through this piece of code:

    if ( in_array( 'qtranslate/qtranslate.php', apply_filters( 'active_plugins', get_option( 'active_plugins' ) ) ) ) { 
        require( get_template_directory() . '/inc/catchkathmandu-qtranslate.php' );

    But if one uses mqTranslate the path for the plugin is different: should be mqtranslate/mqtranslate.php. So, I’ve slightly modified the file and now everything is ok without needing to apply other changes:

    if ( in_array( 'qtranslate/qtranslate.php', apply_filters( 'active_plugins', get_option( 'active_plugins' ) ) ) ||
    in_array( 'mqtranslate/mqtranslate.php', apply_filters( 'active_plugins', get_option( 'active_plugins' ) ) ) ) { 
        require( get_template_directory() . '/inc/catchkathmandu-qtranslate.php' );

    So, Sakin, I believe you might include something like this in upcoming versions.

    Thank you again!


    @Jaume: Ok so you mean that we add in support for mqtranslate plugin as well. Ok sure we will add this in future version update. Thanks.

Viewing 9 posts - 1 through 9 (of 9 total)
  • The topic ‘Subtitle and Footer translation’ is closed to new replies.