Translating Labels set in a View (in fields and template)

  • Resolved maryb1

    (@maryb1)


    2 weeks, 1 day ago

    Hi,

    I’m using WPML and after creating a View where I added labels (in Fields tab), I can’t see those labels for translation in WPML even after rescanning for new strings. I read this support file (https://docs.acfviews.com/templates/multilingual), where it says:

    Advanced Views uses the built-in WordPress translation function __('field label', 'themeDomain') for all View and Card labels. This allows you to translate labels seamlessly using your preferred multilingual plugin, eliminating the need for creating a separate View or Card for every language.

    I thought this meant the labels would appear automatically in the strings to translate. Since that didn’t work, I did activate the File system storage, and it did create a multilingual file in my child theme with all the labels set in the Fields tab of the View and also the one I manually added to the template (ex: {{ __(‘Coordonnées’, ‘acf-views’) }}).

    I noticed that in the multilingual file, the labels that I set in Fields tab of the View do not have a textdomain. Does this mean I have to manually edit this language file to add a textdomain?

    The label I added manually in the template does have the textdomain I specified in the template. I wasn’t sure which textdomain to use: acf-views or my theme’s (generatepress), but either way, this label also does not show up in the string translations in WPML.

    So after trying all this, none of my labels seem translatable. I must be missing something. Can you help with this?

    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author WPLake

    (@wplakeorg)

    Hi @maryb1

    Thank you for using Advanced Views!

    Please see the following:

    1. File system mode

    To use automatic string detection you should keep the FS mode active (as you have it now).

    When it’s active, every View and Card upon saving updates the ‘multilingual.php’ file with detected strings, as described in the FS docs: https://docs.acfviews.com/templates/file-system-storage#views-folder

    2. Manual amending of ‘multilingual.php’

    You should not amend this file manually, it’s generated automatically and overridden upon each save.

    3. Text domain

    AVF picks up the text domain automatically, based on the ‘Text Domain’ setting, defined in the heading of style.css of your theme (https://developer.www.ads-software.com/themes/basics/main-stylesheet-style-css/).

    So it seems that you use a child theme, which doesn’t define the Text domain, you’ll need to define it.

    It can be the same value as your parent theme, or your own, but never “acf-views”.

    After that, save target Views & Cards (or disable/enable FS mode to regenerate all, in case you’ve multiple items). Then scan the theme again and the strings will appear in your translation tool.

    Thread Starter maryb1

    (@maryb1)

    It worked! Thanks so much for the quick reply and clear instructions.

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