• Resolved daro2013

    (@daro2013)


    Dear Sir,

    I like to translate the string on a registration form created by a plugins called UserPro.

    I read your quick guide and dont see any thing related to plugins translation; it is only for theme?

    I did try to translate some strings on that plugins, but nothing is translated on browser. Then I created a folder similar to the theme like:

    /wp-content/languages/loco/plugins

    on the server, but nothing has been translated.

    Can you please help with that?

    Cheers
    Daro

    The page I need help with: [log in to see the link]

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author Tim W

    (@timwhitlock)

    Plugin translations is much like theme translation in most ways that matter to the end user. Please be more specific about your problem and post a download link to what you’re translating.

    Thread Starter daro2013

    (@daro2013)

    Hi,

    Thank you for a prompt reply. Do you a PO file?

    Basically, UserPro does not translate all strings on its front end; only part of it; I cannot post my life site here as it is under development.

    Can you please clarify what you need from me?

    Cheers

    Thread Starter daro2013

    (@daro2013)

    and my theme has a built-in Polylang plugins which is used mainly to translate the theme without issues.

    For plugins such as UserPro, it cannot translate using PO and MO file.
    Is it ok to use Loco on top of Polylang?

    I have tried to translate more string on UserPro, but nothing is translated; This is what I did:

    Loco Tranlsate –> Plugins –> UserPro –> Create a new template in /wp-content/loco/plugins/
    Then add a new language

    then go to Loco Editor to translate the strings on UserPro plugins.

    Nothing has been translated on Front end at:

    https://www.45kjdsa4e.eu/login/

    or:

    https://www.45kjdsa4e.eu/register/

    Do you think what is wrong with that?

    Cheers

    Plugin Author Tim W

    (@timwhitlock)

    I can’t advise on your use of Polylang, but Loco Translate is simply a file editor. I don’t know of any reason why another plugin would stop you opening, editing and saving PO files. If this part is working then Loco Translate has done its primary job.

    Translations not showing up is rarely a problem with Loco Translate and is usually due to the theme/plugin being translated. See the most asked questions: https://localise.biz/wordpress/plugin/faqs

    To establish why your strings are not loading I would need to install the UserPro plugin. This is why I asked you to post a download link. If your plugin is commercial then you’ll have to resolve the problem with the vendor.

    Thread Starter daro2013

    (@daro2013)

    Hi sir,

    I have a license and seems unlimited as I have installed it on three websites without issue.

    The vendor did help to translate, but he wont show me the way he translate; and I am frustrated as I need to change some strings on Registration form often, and I need to go through that plugins’ support. That is why I like to use Loco to translate that plugins independently

    I can send you that plugins to download, but how can I send you a license key?

    Cheers

    Thread Starter daro2013

    (@daro2013)

    UserPro wont stop me from saving/editing PO file using PoEdit. However, some strings in its PO file cannot translated; I mean, I can insert new strings after creating a registration into its PO file and translate it using PoEdit to generate MO file, then upload to its relevant directory. But nothing has been translated; only a couple of them which is created by default of UserPro can be translated. The vendor has to translate them in a secret way (he does not tell me even I have asked repeately) to translate them. I am very frustrated with this plugins.

    Many thanks in advance.

    Regards

    Thon

    Plugin Author Tim W

    (@timwhitlock)

    You will have the same problems using POEdit, or any text editor because your problem is not with the editing software.

    Please don’t send me your license key. I don’t provide help debugging commercial plugins.

    If your plugin vendor won’t help you translate their product, I suggest you switch to an open source plugin which follows WordPress internationalization standards and whose code is open to public scrutiny.

    Loco Translate will automatically work with any plugin that follows WordPress standards and can be configured to work with unconventional patterns if needed.

    Thread Starter daro2013

    (@daro2013)

    More: I have also try to translate with WP-PostViews plugins which is free here:

    Nothing has been translated although I could see PO and MO files have been translated in /wp-content/languages/loco/plugins/

    https://en-gb.www.ads-software.com/plugins/wp-postviews/

    Could you please test that plugins why Loco cant translate?

    Cheers

    Plugin Author Tim W

    (@timwhitlock)

    Sure. I’ve downloaded it. Can you provide an example string that does not translate?

    Thread Starter daro2013

    (@daro2013)

    views and Views. The first one is displayed on front page; not sure where the second one is displayed.

    Plugin Author Tim W

    (@timwhitlock)

    The wp-postviews plugin has custom blocks of text that you save in the admin area under *Settings > PostViews*

    The text “views” is in the PO file because it’s used when the following “Most Viewed” template is initially constructed:

    '<li><a href="%POST_URL%" title="%POST_TITLE%">%POST_TITLE%</a> - %VIEW_COUNT% '.__('views', 'wp-postviews').'</li>'

    Once saved into the database the “views” string is baked in and won’t be translated again. This is a common [deliberate] mistake by plugin authors that causes lots of people confusion.

    You will have to go into the options screen and change the whole template, but then switching language will not change the text, nor will editing the PO/MO files.

    As the issue is unconnected with Loco Translate I am marking this as resolved.

    Thread Starter daro2013

    (@daro2013)

    This means your Loco plugins cannot translate most major PLUGINS; it may be used for theme only.

    Thanks for your help.

    Plugin Author Tim W

    (@timwhitlock)

    That statement is nonsense and after the all the time I’ve given you today it’s pretty rude.

    Using translation files to embed text into database-stored options is bad practice and any good quality plugin (or theme) will avoid such methods. It makes translation harder and confuses users.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘How can I use loco to translate a plugins?’ is closed to new replies.