Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Ewout

    (@pomegranate)

    You can simply use the translated string directly without _e()
    For multilingual setups with WPML or Polylang we require the Professional extension. If you already have that, please send us an email at [email protected], including the code you are currently using and we’ll do our best to help with this!

    Thread Starter skinperforator

    (@skinperforator)

    But I want it to function in both languages like the rest of the template does.
    We use the frontend in English and the backend in another language.

    Plugin Contributor Ewout

    (@pomegranate)

    I see, for custom strings you’ll have to use your child theme or theme translations, which have their own textdomain. You can do that via Loco Translate too, and then simply use that textdomain in the _e() function (using ‘your-child-theme’ as the domain in this example):

    
    _e( 'Custom text', 'your-child-theme' );
    
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Add translation for custom field’ is closed to new replies.