WordPress.org

Ready to get started?Download WordPress

Forums

Polylang
[resolved] Warnings from 'Codestyling Localization' plugin (4 posts)

  1. weeix
    Member
    Posted 1 year ago #

    Hello Chouby,

    First I must thank you for your great plugin. I used to install qTranslate for my bilingual project, but your multilingual plugin seems very promising that I'd like to give it a try.

    The 'Codestyling Localization' (CL) plugin keeps warning me about other plugins and themes, so I decide to report it to every developers. I'm not very experienced with plugin developing so I don't know if it's a false warning or not, but I think it might be useful.

    1. CL report this after I turn on Polylang:

    STRICT Error: [2048] Only variables should be passed by reference
    D:\\xampp\\htdocs\\hynae\\wp-includes\\pomo\\mo.php on line 210

    2. CL suggest about using load_plugin_textdomain instead of load_textdomain

    Picture: http://www.fileden.com/files/2010/11/3/3007256/polylang098.png

    Thanks for hearing me out, Wee.

    http://wordpress.org/extend/plugins/polylang/

  2. Chouby
    Member
    Plugin Author

    Posted 1 year ago #

    1. I don't have the error you reported (I am using CodeStyling Localization 1.99.29). Have you some special debug settings?

    2. I am aware of the compatibility warning displayed by CodeStyling Localization. I anm using load_plugin_textdomain to load the polylang textdomain.

    In Polylang, you have the possibility to choose the language from content (see Polylang settings). That means that the language code is not included in the url for posts and pages. This has some pros and cons. Among this, Polylang needs to delay the textdomain load (normally done before the content is known). So Polylang uses load_textdomain to do this. This function is convenient as I don't need to know what sort of text domain it is (default, plugin, theme). To avoid this compatibility warning would need more complex code and, up to now, no issue (except this warning) was reported. I am using both plugins and never got any conflict.

  3. weeix
    Member
    Posted 1 year ago #

    Maybe it's about the php in my machine - I'm using version 5.4.7

    It seems that load_textdomain is essential for multilingual plugins since they have to localize WP, themes and other plugins.

  4. Chouby
    Member
    Plugin Author

    Posted 1 year ago #

    I am using 5.4.7 too. load_textdomain is useful only because, depending on the chosen option, Polylang defers text domain loading. It is not needed when the language code is added to all urls (because in that case, it is possible to set the language before WP, plugins and themes load load the text domain).

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic