Support » Plugins and Hacks » Polylang » [Plugin: Polylang] "Site Title" and "Tagline" are not changing

Viewing 15 replies - 16 through 30 (of 49 total)
  • Plugin Author Chouby

    (@chouby)


    You can also forget about the code above and just download the development version (0.9.2.3) in which I included it.
    http://downloads.wordpress.org/plugin/polylang.zip

    Terrific Chouby. That’s really great. The Blog title and tagline are now correctly translated.

    I’m not sure if I’d better start a new thread for the following, but since were here…
    I just noticed that the only thing that doesn’t translate is the posts Metabar. When you look at http://www.janpeeters.nl/blog-english/ the ‘posted on [date]’ string is still in Dutch. Could this have to do with the same issue? Or should we do something else to solve this.

    Thanks again!

    It works perfect with Headway theme too. The Blog title and tagline are now correctly translated.

    Thank you Chouby!!

    Chouby, sorry, the non-translating metabar has nothing to do with Polylang I guess. I type it somewhere in the theme so I have to find a way to translate these in some other way. Thanks again for the dev build it works great.

    Plugin Author Chouby

    (@chouby)


    I guess these are strings which are stored in theme options. The main difficulty is to find the option where they are stored. Then, you can filter the option and, on admin side, register the strings with ‘pll_register_string’, on frontend side, translate them with ‘pll__’.
    Examples in the links I gave you above can help. The best, however, is to create a separate personal plugin.

    I wonder. Does your theme contain a file name ‘wpml-config.xml’?

    Hi, I haven’t been able to find a file with that name.
    I know they have a repository for translating the Pagelines Framework in other languages, but I’m afraid that this is only for the back-end and not for strings manually entered by end user.
    More info on their localisation here:
    http://www.pagelines.com/translation-localization-center
    http://www.pagelines.com/translate/projects/pagelines-framework

    I’ll look into the plugin method. Thanks again.

    Hi Chouby,

    I was wondering. Is it a idea for a feature of Polylang that people could manually add strings on your Strings translation page for non-generic strings? I figured that if you can find the right string that is called from any theme you could add it there and fill in the translations?

    Best, Jan

    Me again, I’m ping-ponging between the WP forum and Pagelines forum to try to solve this. I’ve started a thread on the PL forum with the request where the right options can be found and if there is a wpml-config.xml file. Hopefully we can tackle this and provide the people that are using Pagelines Framework with a solution.

    Plugin Author Chouby

    (@chouby)


    I asked you about the wpml config file as it would have been a clue to know if the theme was compatible with WPML.

    It’s good to see that Pagelines source code is freely available:
    http://phpxref.pagelines.com

    I found here that the theme manages to be compatible with WPML.
    I am not sure however that everything is managed in the function ‘pagelines_magic_parse’ in the file includes/library.options.php @ line 277.

    Maybe you can ask the authors to add string translation management by Polylang with something like:

    if (is_admin())
      pll_register_string($key, $string);
    else
      return pll__($string);

    The Polylang API works pretty much the same way as the WPML API, except that there is no group and that you must test ‘is_admin’ as ‘pll_register_string’ is not available on frontend and ‘pll__’ is not available on admin.

    To answer your second post, the problem is not to include a string in the string translation table, but how to tell the theme that it has to use the translated string

    Plugin Author Chouby

    (@chouby)


    FYI, the file ‘wpml-config.xml’ is one way to inform WPML it has to translate a string without using the WPML API. Pagelines uses directly the WPML API

    Wow your a speedy responder, thanks. I will copy-paste your reply to the thread that I just mentioned and see what happens.

    Thanks for the great support!

    Plugin Author Chouby

    (@chouby)


    Why did I not think to this before today??? It should be even easier if Polylang includes the WPML API! Thus all plugins and themes which use it would be compatible with Polylang without effort…

    Could you try the latest development version (0.9.2.4)?
    http://downloads.wordpress.org/plugin/polylang.zip

    It’s a brilliant idea but it’s only working to some extend at the moment. But lets troubleshoot this over the next days because it feels like a smart move. In the following screenshot you can see new strings showing up in the strings screen:
    https://dl.dropbox.com/u/424822/Shared%20Screenshots/Polylang_924.png
    But besides the regular strings only two new show up, those are the titels of two sidebar text widgets that I conditionally show on Dutch and English pages that are about education (‘opleiding’ in Dutch) and Career (‘loopbaan’ in Dutch) To provide for translation I have to have two for each widget.
    How should this WPML API work?
    And is the API freely available?

    Plugin Author Chouby

    (@chouby)


    When I write that Polylang includes the WPML API, it just means that in 0.9.2.4 I created 2 function which have exactly the same names and parameters than in WPML. Thus the theme should believe that it calls WPML functions.

    I’m not sure if I understand you well enough.
    So this means that in this latest test build you added the fields that occurred in the Strings Translation page or text widget titles? and does that mean that more should be added?
    Or do you mean that I should see a difference in the theme admin? That is not the case.
    Sorry that I have difficulty to grasp this.

Viewing 15 replies - 16 through 30 (of 49 total)
  • The topic ‘[Plugin: Polylang] "Site Title" and "Tagline" are not changing’ is closed to new replies.