Dokan issue to use Translated language

  • Resolved microbit

    (@microbit)


    7 years, 3 months ago

    After 2.6 verion uptade until now, the PO and MO file connot be used in dokan lite or pro.
    I’ve tried many ways and solved the lite verion issue.
    the issue was text-domain name in the dokan-lite.php
    and the code in below must be changed.

        public function localization_setup() {
        load_plugin_textdomain( 'dokan-lite', false, dirname( plugin_basename( __FILE__ ) ) . '/languages/' );
    }

    but one of my customers had same issue on Pro version and I didn’t success to resolve the problem with that way I used it before in lite verion.

    thanks.

Viewing 3 replies - 1 through 3 (of 3 total)

  • @microbit, Dokan lite, and pro have separate text-domain. So, the file name should be different. Please follow this doc to translate the plugin- https://docs.wedevs.com/docs/dokan/common-questions/translate-dokan-plugin/.

    Thread Starter microbit

    (@microbit)

    thanks for your replay.
    yes I did it but still didn’t work.

    if you look at the orginal lite version you will see the text domain in the dokan-lite.php is wrong.
    that why I replaced the code that I send on above post. its customized.
    the new vertion 2.6.8 that recently updated and problem its back!

    and in pro version its not mentoined the text domain in dokan.php in the plugin root.
    there is any chance to resolve this?

    • This reply was modified 7 years, 2 months ago by microbit.

    Hi,

    Thanks for pointing this out. We will update these issues in next release.

    The reason the function text-domain was ignored as ORG plugins take domains from the Text Domain tag at top of main file which is declared as ‘dokan-lite’. But from your case it seems like we should keep it in both places.

    Thanks again.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Dokan issue to use Translated language’ is closed to new replies.