Translating Field Labels and Form Labels

This topic contains 30 replies, has 3 voices, and was last updated by  Colin Whiteside 3 years, 10 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket

Tagged: 

  • Author
    Posts
  • February 28, 2020 at 7:35 am #7401

    Colin Whiteside
    Full Member
    Post count: 46

    Hi there,

    I can’t seem to figure out how to translate field and form labels for items on the account form that I have added (fieldsets and text areas).
    Option values for multi-select fields that I added show up in wpml (string translation) and translate perfectly.

    Other ‘stock’ field labels were translatable via wpml string translation, but not the ones I have added.

    If I switch to a different language (on the backend) and change the labels for this language, this translation now shows up for all languages. So that doesn’t work either.

    Everything else is translating fine.

    Please advise.
    Thank you,
    Colin

    February 28, 2020 at 6:31 pm #7418

    Alex Rollin
    Moderator
    Post count: 27815

    Please try this: https://wpgeodirectory.com/docs/translating-custom-fields/

    Let us know how it goes

    March 5, 2020 at 1:10 am #7495

    Colin Whiteside
    Full Member
    Post count: 46

    Hi Alex,

    Thanks, but no, it did not work. Ran the tool under GeoDirectory – Status – Tools – DB text translation
    and they did not show up in string translation.

    I noticed under UsersWP – Status – Tools – … there is no such tool.

    Thanks,
    Colin

    March 5, 2020 at 1:12 am #7496

    Alex Rollin
    Moderator
    Post count: 27815

    I have flagged your topic for the developers to check the status of this feature for UsersWP.

    March 11, 2020 at 10:03 am #7577

    Patrik
    Moderator
    Post count: 1971
    This reply has been marked as private.
    March 11, 2020 at 4:23 pm #7584

    Colin Whiteside
    Full Member
    Post count: 46
    This reply has been marked as private.
    March 12, 2020 at 10:01 am #7589

    Patrik
    Moderator
    Post count: 1971
    This reply has been marked as private.
    March 12, 2020 at 4:15 pm #7598

    Colin Whiteside
    Full Member
    Post count: 46
    This reply has been marked as private.
    March 13, 2020 at 9:56 am #7610

    Patrik
    Moderator
    Post count: 1971
    This reply has been marked as private.
    March 13, 2020 at 5:52 pm #7616

    Colin Whiteside
    Full Member
    Post count: 46
    This reply has been marked as private.
    March 15, 2020 at 9:24 pm #7620

    Colin Whiteside
    Full Member
    Post count: 46
    This reply has been marked as private.
    March 17, 2020 at 1:14 pm #7638

    Patrik
    Moderator
    Post count: 1971
    This reply has been marked as private.
    March 24, 2020 at 2:38 am #7680

    Colin Whiteside
    Full Member
    Post count: 46
    This reply has been marked as private.
    March 24, 2020 at 5:37 am #7684

    Patrik
    Moderator
    Post count: 1971

    Hi,

    As per your requirements, we need to work on the compatibility with WPML for custom fields. We already have compatibility for pages of UWP. We will look into this and fix it as soon as possible. You can try to translate the string using .PO file and check if it works for you or not. Regarding the admin interface with different languages in WPML, the fields will override the changes if you change from any language as we have to look into the compatibility for this.

    Regards,
    Patrik

    March 27, 2020 at 4:27 am #7738

    Colin Whiteside
    Full Member
    Post count: 46

    Hi Patrik,

    It did not work, to add the strings using a .PO file… it seems the dynamic strings are not wrapped in a GetText call? (See https://wpml.org/faq/language-setup/)

    We would appreciate it greatly if this could be fixed.

    This shows up in: the account, profile and users pages/widgets, and the uwp output location widget…

    Thank you so much,
    Colin

  • Author
    Posts
Viewing 15 posts - 1 through 15 (of 31 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket