# Multi-language compatibility, $domain defaults to theme\_slug

**URL:** <https://forum.pinegrow.com/t/multi-language-compatibility-domain-defaults-to-theme-slug/7097>\
**Category:** Feature Request\
**Tags:** wordpress, woocommerce\
**Created:** [October 12, 2022, 7:49am UTC](https://forum.pinegrow.com/t/multi-language-compatibility-domain-defaults-to-theme-slug/7097 "2022-10-12T07:49:18Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![madjedo](https://avatars.discourse-cdn.com/v4/letter/m/cc9497/32.png) [@madjedo](https://forum.pinegrow.com/u/madjedo)\
**Post date:** [October 12, 2022, 7:49am UTC](https://forum.pinegrow.com/t/multi-language-compatibility-domain-defaults-to-theme-slug/7097/1 "2022-10-12T07:49:18Z")

</div>

Pinegrow uses Wordpress \_\_e function to display text that can be translated. This is good. This means we can translate the whole WP theme and maintain compatibility with multilanguage plugins such as WPML.

However, the $domain (Unique identifier for retrieving translated strings) always defaults to whatever your theme slug is. Since we currently cannot change the $domain in Pinegrow this can cause issues when developing multilanguage e-commerce sites that use WooCommerce.

WooCommerce is already translated to multiple languages. Since Pinegrow defaults to using your theme\_slug by default, even for WooCommerce elements, this means WordPress wont be able to use the already translated strings that comes with WooCommerce.

WooCommerce is just one example, but I am sure there are more plugins out there that has their own domain for this and comes shipped with already translated text strings.

The best solution is to give us control to be able to change the $domain or default to use ‘WooCommerce’ domain for Woo elements.

More information and documentation regarding the \_\_e function:

> **[\_e() | Function | WordPress Developer Resources](https://developer.wordpress.org/reference/functions/_e/)**
>
> Display translated text.

---

<div class="post-metadata">

**Author:** ![adamslowe](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/adamslowe/32/4590_2.png) [@adamslowe](https://forum.pinegrow.com/u/adamslowe)\
**Post date:** [October 12, 2022, 4:16pm UTC](https://forum.pinegrow.com/t/multi-language-compatibility-domain-defaults-to-theme-slug/7097/2 "2022-10-12T16:16:24Z")

</div>

Nice catch! I was actually going to start a Pinegrow conversion project next month with just this use case, and hadn’t considered this issue. Here’s to hoping that Pinegrow delivers that capability or at least a suitable workaround.

---

<div class="post-metadata">

**Author:** ![madjedo](https://avatars.discourse-cdn.com/v4/letter/m/cc9497/32.png) [@madjedo](https://forum.pinegrow.com/u/madjedo)\
**Post date:** [October 12, 2022, 4:43pm UTC](https://forum.pinegrow.com/t/multi-language-compatibility-domain-defaults-to-theme-slug/7097/3 "2022-10-12T16:43:06Z")

</div>

You can still translate the elements by creating po file. But you wont be able to use already translated woocommerce strings.

---

<div class="post-metadata">

**Author:** ![Pinegrow\_Learner](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@Pinegrow\_Learner](https://forum.pinegrow.com/u/Pinegrow_Learner)\
**Post date:** [November 2, 2022, 5:48am UTC](https://forum.pinegrow.com/t/multi-language-compatibility-domain-defaults-to-theme-slug/7097/4 "2022-11-02T05:48:11Z")

</div>

@matjaz Any solution for this?

---

<div class="post-metadata">

**Author:** ![madjedo](https://avatars.discourse-cdn.com/v4/letter/m/cc9497/32.png) [@madjedo](https://forum.pinegrow.com/u/madjedo)\
**Post date:** [December 26, 2022, 7:19am UTC](https://forum.pinegrow.com/t/multi-language-compatibility-domain-defaults-to-theme-slug/7097/5 "2022-12-26T07:19:07Z")

</div>

Nope!

I dont think I should even have posted this in “feature request”. Looks more like this was overlooked and forgotten about. Probably wont be using Pinegrow for next project. Multi language too important for me.

---

<div class="post-metadata">

**Author:** ![Emmanuel](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/emmanuel/32/6294_2.png) [@Emmanuel](https://forum.pinegrow.com/u/Emmanuel)\
**Post date:** [December 26, 2022, 12:58pm UTC](https://forum.pinegrow.com/t/multi-language-compatibility-domain-defaults-to-theme-slug/7097/6 "2022-12-26T12:58:55Z")

</div>

@madjedo message received & heard.

---

<div class="post-metadata">

**Author:** ![MichelyWeb](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/michelyweb/32/6652_2.png) [@MichelyWeb](https://forum.pinegrow.com/u/MichelyWeb)\
**Post date:** [February 3, 2024, 11:28am UTC](https://forum.pinegrow.com/t/multi-language-compatibility-domain-defaults-to-theme-slug/7097/7 "2024-02-03T11:28:35Z")

</div>

Any news regarding this feature request?