• Resolved Tomistar

    (@tomistar)


    Hello.

    First question:
    Its possible to make frontend view in different language than admin pages without language switcher in frontend. How I make this possible?

    Secound question:
    In many places where I need translation is not blue border on the left side and I can not translate. Is it possible to add translations in those places?

    Thank you.

    https://ww.wp.xz.cn/plugins/qtranslate-x/

Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Author Gunu

    (@grafcom)

    @tomistar

    First question:
    I’m not sure I understand you correctly, default language front-end you can set in the settings. Default language in admin site you can set with the language button top right in admin bar.

    Second question:
    Read this Integration Guide

    Thread Starter Tomistar

    (@tomistar)

    First question solved. You understand correct but i had to disable Detect Browser Language and it work now.

    What about second question. Its possible?

    Plugin Author Gunu

    (@grafcom)

    it depends, can you use the information in the Integration Guide?

    In many places where I need translation is not blue border on the left side and I can not translate.

    where are those fields?

    Did you try it with the language codes in that fields? for example:
    `[:nl]Dutch tex[:de]German text[:en]English text

    Thread Starter Tomistar

    (@tomistar)

    These fields are everywhere, in most cases, I have a blue border to a title and description, but I do not have in other fields such as (Shortcodes, keyword or slug, text links, …) For exmaple: I have also slider section in admin but no blue borders where i can add/edit sliders.

    But the proposed syntax works. I have not yet inserted in all fields but there where I inserted it works.

    Thank you. For now problem solved.

    Plugin Author Gunu

    (@grafcom)

    look also here for id and class an try this

    Is it possible to translate theme custom fields?

    Thread Starter Tomistar

    (@tomistar)

    Thank you

    Plugin Author Gunu

    (@grafcom)

    @tomistar
    You are welcome!

    You can review this plugin to help other people to find out the value.

    Thread Starter Tomistar

    (@tomistar)

    Hello.

    I read what you sent me.
    I put ids into costum fields.
    My costum field id field: autotrader_header_title_blog autotrader_content_bottom_blog seek_property_name_singular seek_property_name_plural slug

    For example:
    <input class=” tfuse_option” name=”seek_property_name_singular” id=”seek_property_name_singular” type=”text” value=”Vozilo”>

    I use seek_property_name_singular.

    But nothing change in admin. Not showing language switching buttons and blue border.
    If i use this syntax [:nl]Dutch tex[:de]German text[:en]English text for seek_property_name_singular its working in front end.

    Should I do something else also?

    Plugin Author Gunu

    (@grafcom)

    what happens if you put under class tfuse_option ?

    Thread Starter Tomistar

    (@tomistar)

    i also tried but its the same. Do not show blue border and language switching buttons. Also not working.

    Plugin Author Gunu

    (@grafcom)

    hmmm then you must use the languages codes or make a JSON-encoded configuration file as described in the Integration Guide.

    Thread Starter Tomistar

    (@tomistar)

    I almost did it and understand how it works. In some cases everything works.
    In another cases everything working just when save it,save just in one language. My code when save it in one language:

    “admin”:{
    “pages”:{“admin.php”:””},
    “forms”:{
    “edittag”:{
    “fields”:{
    “autotrader_header_title_blog”:{}
    }
    }
    },
    “js-exec”:{“edit-tag-exec”:{“src”:”./admin/js/edit-tag-exec.min.js”}}
    }
    ,

    working code:
    “edit-tag”:{
    “pages”:{“edit-tags.php”:”action=edit”},
    “forms”:{
    “edittag”:{
    “fields”:{
    “name”:{},
    “description”:{},
    “autotrader_header_title_cat”:{}, //add it and works
    “autotrader_content_bottom”:{}, //add it and works
    “slug”:{}, //add it and save it just in one language
    “parent”:{ “encode”:”display” }
    }
    }
    },
    “js-exec”:{“edit-tag-exec”:{“src”:”./admin/js/edit-tag-exec.min.js”}}
    }
    ,

    I cant figure out what its wrong.

    Plugin Author Gunu

    (@grafcom)

    For slugs you need also qTranslate Slug, doesn’t work this way.

    Thread Starter Tomistar

    (@tomistar)

    Okey:). Slug is not so important. Why save header title blog in last entered language?

    Code:
    <input name=”qtranslate-fields[autotrader_header_title_blog][sl]” type=”hidden” class=”hidden” value=”sl”>
    <input name=”qtranslate-fields[autotrader_header_title_blog][en]” type=”hidden” class=”hidden” value=”sl”>
    <input name=”qtranslate-fields[autotrader_header_title_blog][de]” type=”hidden” class=”hidden” value=”sl”>
    <input name=”qtranslate-fields[autotrader_header_title_blog][qtranslate-separator]” type=”hidden” class=”hidden” value=”[“>
    <input class=” tfuse_option qtranxs-translatable” name=”autotrader_header_title_blog” id=”autotrader_header_title_blog” type=”text” value=”sl”>

    Create all three entries with last entered value.

    Plugin Author Gunu

    (@grafcom)

    Why save header title blog in last entered language?

    the title does not work by default? What theme do you use?

Viewing 15 replies - 1 through 15 (of 18 total)

The topic ‘two questions’ is closed to new replies.