Support » Plugin: Nelio Content - Social Media Marketing Automation » Translation BUG after update

  • Resolved Anonymous User 17115093

    (@anonymized-17115093)


    All translations stoped working after the last update! After 1 year (there was no any problem). We may move files to any folder – always the same. Only EN!

    • This topic was modified 1 month, 1 week ago by Anonymous User 17115093.
Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author David Aguilera

    (@davilera)

    Hi! What language are you using? The new version we released is a complete redesign of the plugin, and there are several strings that may not have been translated yet. Right now, they’re only available in Spanish and Catalan, as you can see here.

    Also, we identified a couple of issues (#223 and #225) in the tool used by WordPress to extract the strings that can be translated, which means that, until it’s fixed and addressed, some strings will remain in English.

    Anonymous User 17115093

    (@anonymized-17115093)

    100% is in English! Nothing works! Everything stoped – it is not an update but a BUG! Maybe you also changed the name of the default PO file? There isn’t any POT incuded (with the plugin), as well!

    • This reply was modified 1 month, 1 week ago by Anonymous User 17115093.
    • This reply was modified 1 month, 1 week ago by Anonymous User 17115093.
    • This reply was modified 1 month, 1 week ago by Anonymous User 17115093.
    Plugin Author David Aguilera

    (@davilera)

    After discussing with OP via email, we’ve finally identified what’s amiss.

    Apparently, they had translated Nelio Content using Loco Translate, which relies on a pot file being included in the plugin.

    Since version 2.0, pot files are no longer included in the plugin’s source code because we assumed all translations would be managed via WordPress.org. If you’re interested in retrieving a po/pot file, you can do so using the Export feature provided by WordPress.org’s translations.

    Since translations do work when generated via WordPress.org, I’m marking this issue as resolved.

    Anonymous User 17115093

    (@anonymized-17115093)

    Tested on 3 fresh instalations:

    1) On 2 of them we have such info (after install):
    plugins/nelio-content/includes/utils/functions/helpers.php on line 110

    2) We DO NOT use Loco. We have just downloaded from WP original PO file wp-plugins-nelio-content-stable-pl (669 strings). Changed its name to nelio-content-pl_PL. Translated some strings in Poedit. Uploaded to 3 directories (not 1 but 3 possible) and…

    Everything is always in ENGLISH!

    • This reply was modified 1 month, 1 week ago by Anonymous User 17115093.
    Plugin Author David Aguilera

    (@davilera)

    1) On 2 of them we have such info (after install):
    plugins/nelio-content/includes/utils/functions/helpers.php on line 110

    Thanks! That’s an issue unrelated to the translations. But thanks for reporting it. We had already identified it and we’ll release the fix in the next hours.

    2) We DO NOT use Loco. We have just downloaded from WP original PO file wp-plugins-nelio-content-stable-pl (669 strings). Changed its name to nelio-content-pl_PL. Translated some strings in Poedit. Uploaded to 3 directories (not 1 but 3 possible) and…

    The issue is quite simple: Nelio Content 2.x uses the new JavaScript i18n feature in its UI, which was introduced in WordPress 5.0 back in 2018. This means that, if you want to have a translated UI, you need to:

    1. Translate the plugin as always, either in GlotPress or via the POT file (and using whatever program you like)
    2. Generate a set of JSON files that will contain the specific strings used in each script included in our plugin

    I think the problem lies in your skipping the last step. I know it’s a cumbersome process to manually generate those files using a tool like po2json – that’s why I insist on translating the plugin via GlotPress (it’s a built-in feature) and that’s why I don’t consider this thread an issue.

    Anonymous User 17115093

    (@anonymized-17115093)

    After 2 years, Nelio Conten is the only plugin we gave up on all our projects. We understand that the plugin is changing, but for over 200 websites we have, it’s the only time we spend 2 days discussing problems that shouldn’t be there.

    We have no translation problems on any of the 200 pages, and if they do appear, they concern missing strings in POT / PO and are quickly updated.

    I do not fully understand how the translation system works here because yesterday we were assured that at least some of the translations should be visible and nothing works.

    Thank you for GlotPress – the plugin has 600 users after 4 years. Loco has over 1M, and you completely ignored Loco users.

    Plugin Author David Aguilera

    (@davilera)

    When I said GlotPress I obviously meant the official WordPress mechanism for translating plugins. I insist: if you translate the plugin there, everything will work.

    You and I wasted 2 days discussing this issue because you’re not reading what I’m telling you: Nelio Content 2.x does not only need a PO/MO file – it also needs several JSON files that should contain all the translations required by each of its JavaScript files. If you want to translate the plugin by yourself but then fail to generate these assets, it’s no wonder things aren’t working as expected.

    Regarding Loco Translate, they explicitly mention in their website that it’s currently unable to generate the required assets:

    There is currently no support for JSON language packs used with wp_set_script_translations.

    But I assume this isn’t an issue because, as you said:

    We DO NOT use Loco.

    Anonymous User 17115093

    (@anonymized-17115093)

    I don’t think you understand. You came up with some changes to the plugin without analyzing all the pros and cons. It could have been done differently, better prepared, notified users or created a seamless translation mechanism.

    You come up with something that doesn’t work!

    We use Loco, but when necessary, we use Poedit, WPML etc. – understand that if the user (and the client in total, because we also had a Pro license) on his 200 pages has no problem with translations and only the problem occurs in 1 plugin, then something is not right here as it should be.

    Plugin Author David Aguilera

    (@davilera)

    Our plugin doesn’t do anything fancy with translations: it uses standard WordPress tools to internationalize both PHP code and JavaScript code.

    I understand you have some specific needs – you need to craft your own translations and joining a Polyglots team and translating the plugin on WordPress.org is not an option for you. That’s totally fine – you simply need to manually generate the required JSON assets. Please read the documentation on how to do it manually or wait until Loco Translate releases an update that’s compatible with it and simplifies the overall process.

    Now, if you don’t want to do any of that because you don’t need to with other plugins… well, I can definitely understand. But please stop complaining over and over again about the same issue when I’ve already told you what you need to do to get things up and running.

    Anonymous User 17115093

    (@anonymized-17115093)

    We stopped using the plugin – that’s adequate comment, and you still don’t understand anything. Good luck!

Viewing 10 replies - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.