Language Files NOT connected to .pot file and Link settings are wrong

  • Resolved terrimorgan

    (@terrimorgan)


    7 years, 10 months ago

    ref: Loco-Translate
    Errors 

    No translations found for "simple-membership"
Additional files found
This bundle isn't fully configured, so we don't know what the following files are for. Click the setup tab to complete the bundle configuration.

    Have tried several settings. None work. The translation files are not recognized. And, there appears to be some other configuration problem with the plugin — if I try to sync the source file swpm.pot (340 strings) the file is mostly deleted and 4 strings are updated. I have several other plugins working just fine. Installed wp-members and it had none of these problems. Unfortunately, I would have had to spend hours translating it into Simplified Chinese.

    Also, the link settings for Password reset will NOT allow me to enter a proper path for the translated pages. There is a /path-here/ option which removes the language selector (references the site root) making the page useless or a full path setting that goes to one and only one language — whatever is in the URL.

    What should happen?

    The language files should sync properly so the system can recognize them.

    The URLs for the pages should allow a generic path/ so the language selector can be maintained.

    • This topic was modified 7 years, 10 months ago by terrimorgan.
Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support mbrsolution

    (@mbrsolution)

    Hi, which language files are you referring to?

    Regards

    Thread Starter terrimorgan

    (@terrimorgan)

    Which particular language is Irrelevant. Totally irrelevant.

    The problem, as I stated clearly, is that NONE of the language files are recognized. They are present, and as the message, which I posted states:

    Additional files found
    This bundle isn’t fully configured, so we don’t know what the following files are for. Click the setup tab to complete the bundle configuration.

    There is nothing anywhere that indicates what the problem is, what’s (obviously) missing, or what can be done to correct this failure.

    Plugin Support mbrsolution

    (@mbrsolution)

    Thank you for reporting this. The plugin developers will investigate further your issue.

    Kind regards

    Plugin Support mbrsolution

    (@mbrsolution)

    Hi, I decided to check Loco Translate plugin and it is working for me. So there must be a plugin conflict somewhere in your site. Can you deactivate all of your other plugins except this one and Loco Translate. Then check again.

    Let me know how you go.

    Thank you

    Thread Starter terrimorgan

    (@terrimorgan)

    Of those installed plugins which are not critical and which deactivating will not destroy my site, there was no change. I cannot disable let alone remove every single plugin on my site. Several are essential to my operation.

    I have a business to run and it’s not doing software testing for this plugin. My day cannot be spent installing and reinstalling and removing and installing software.

    First, if your plugin cannot work together with other plugins, it’s useless. It should be coded to be compatible and “play-nice” with just about everything. Actually, anything that doesn’t work in such a simple configuration should not be distributed via WordPress. I have never seen a WordPress site used for anything that did not have multiple plugins running.

    Second, if this lame sort of “try it an see” response is the best you can do, I will find another solution that is actually supported.

    Finally, I expected at the very least a considered response, perhaps a code snippet, a pointer to where the code for the language settings can be modified or something. A “go fish, try again” directive is not useful or helpful.

    Plugin Support mbrsolution

    (@mbrsolution)

    I am sorry to hear you are experiencing so much trouble with our plugin. However I cannot reproduce your issue on either of my sites.

    I hope you find another alternative better than ours.

    My humble apologies.

    Kind regards

    Plugin Author wp.insider

    (@wpinsider-1)

    That other plugin is picking up the wrong “text domain” value for the language file of our plugin which is causing the issue.

    Do the following to correct it:

    1) Go to the “Advanced” setup tab of the “Loco Translate” plugin

    2) Edit the value of the “Text domain” field to the following:

    
swpm

    3) Edit the value of the “File prefix” field to the following:

    
swpm

    Save it and that should do it.

    • This reply was modified 7 years, 10 months ago by wp.insider.
    Thread Starter terrimorgan

    (@terrimorgan)

    This is a responsive answer, but perhaps not one that can be used, at least not in my environment. I’d expect that changing the namespace/file prefix will break the connection to Loco and all the translations I have already completed.

    “That other plugin” — the one that is not registering your translation files — is Loco Translate. Probably because as you say you “do things differently.”

    Loco picks up all of the other plugins I have, including two specialized content presentation plugins and the admin interfaces which I have already translated using Loco. It works extremely well. No problems.

    The only plugin that has been a problem is yours. That’s unfortunate.

    Loco Translate works perfectly with three other membership plugins I tested. Where “Simple Membership” works well is the actual simplicity of configuration for what content should be available to whom. It’s a shame that the translated sets are not compatible with translation tools.

    There are not thousands of translation tool plugins; there are only a few translation tool plugins, Loco (300k), Polylang (200k) – both with free and pro versions, and WPML (paid only) are among the top three, at least according to what I found.

    If you are going to provide multi-lingual features, ‘playing nice’ with translation tools would be something your developers should to pay attention to.

    Thread Starter terrimorgan

    (@terrimorgan)

    Also, from my original post, it seems Simple Membership doesn’t ‘play nice’ with Polylang either. The URL settings override the language selector (Polylang), so instead of allowing Polylang to handle the language changes, it tries to take over. That breaks all (~200) the currently working page-pairs on my site. That’s an even bigger problem.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Language Files NOT connected to .pot file and Link settings are wrong’ is closed to new replies.