• Resolved alimentaridacaio

    (@alimentaridacaio)


    Ciao,
    I’m having trouble with some translations using Loco translate and woo customizer.

    Our theme support says that it’s because we are using also polylang but we just need 2 other words to be translated. As you can see from the link are “Description” and “Additional Info” that we are not able to put in Italian….

    Can you please help?

    The theme we are using is Mildhill.

    Thank you

    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)

    If the theme authors provide a valid POT (template) file in their theme you will be able to translate all the strings they have made available.

    If the strings come from some other plugin, then this applies to the authors of that instead. Do the strings come from WooCustomizer? Can you provide a link for it?

    Thread Starter alimentaridacaio

    (@alimentaridacaio)

    Ciao Tim thank you for your reply.

    The theme has the string but the support team says that the problem is that we are using polylang and not WPML. At the moment we haven’t got the budget for WPML. I don’t understand why the only problem is related to these 2 tabs. The other tabs and translations work perfectly. Also the Review is correctly translated to Italian……

    Plugin Author Tim W

    (@timwhitlock)

    I can’t comment on polylang or WPML, or on commercial themes.

    My plugin is a file editor. Its job is to sync available source strings to a PO file and allow you to save translations into MO files which WordPress can load. If it hasn’t done its job then please provide details. If it has done its job then I can’t help you with your problem.

    Your original Topic title suggest that Loco Translate is not configured to understand WooCustomizer. Is this still something you are asking about?

    Thread Starter alimentaridacaio

    (@alimentaridacaio)

    Yes, here the link of the message I get when I open loco translate and I click on plugin-> woocustomizer

    https://www.alimentaribellagio.com/wp-content/uploads/2020/06/Schermata-2020-06-02-alle-12.34.34.png

    thank you

    Plugin Author Tim W

    (@timwhitlock)

    What file is that?

    The Italian file that ships with woocustomizer belong to Freemius, but these strings are from woocustomizer. Did you create the file? How?

    Thread Starter alimentaridacaio

    (@alimentaridacaio)

    Ciao,
    The Italian was missing so I’ve added it… Clicking on add new language..

    Thank you Tim, I’m sorry but I’ve never used loco translate before but it works perfectly for everyting and not with Woocustomizer…

    Plugin Author Tim W

    (@timwhitlock)

    Clicking add a new language for the main woocustomizer does not produce this warning when I do it.

    Have you attempted to configure the bundle?

    Thread Starter alimentaridacaio

    (@alimentaridacaio)

    How should I configure it in the right way?

    Plugin Author Tim W

    (@timwhitlock)

    You don’t need to configure anything to edit the woocustomizer files. The extra files you see are part of the Freemius plugin that comes bundled inside woocustomizer. We’re not discussing these as far as I’m aware. Your screenshot shows strings from woocustomizer, so I’m trying to work out why what you’re seeing is not what I’m seeing.

    Thread Starter alimentaridacaio

    (@alimentaridacaio)

    What do you want me to do? I mean.. Shall I try to do something that you suggest?

    Thank you so much

    Plugin Author Tim W

    (@timwhitlock)

    I only want to know what you’ve done differently, so I can reproduce your problem. If you don’t know what it could be then this is a dead end.

    Thread Starter alimentaridacaio

    (@alimentaridacaio)

    ok, it’s clear.
    All the other plugins and theme translations are working perfectly with Loco translate.
    The only problem I got is with woocustomizer. So I’ve tried to create a new language (as I need Italian) so I’ve clicked on add language in Woocustomizer section in Loco translate.
    Done that, I see that it’s now working anyway…….
    And the error shown is the one I’ve sent you the picture about: Translation set not known in WooCustomizer

    That’s what I’m facing…

    Thread Starter alimentaridacaio

    (@alimentaridacaio)

    I’m sorry that you could have not helped me.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Translation set not known in WooCustomizer’ is closed to new replies.