wesoli

There is a work around. From what I managed to debug all custom fields fall under the “ultimate-member” text domain when they are generated on the fly to be displayed.

The steps are as follows:
1/ Navigate to: WPML -> String Translation
2/ Scroll to the bottom of the page and look for the title “Auto register strings for translation”
3/ Check the box “Look for strings while pages are rendered”. There will be a performance impact warning and a 2 hours countdown incase you forget this option checked.
4/ There is a button that appears underneath the checkbox. If you select it a popup window appears and you can limit which text domain is scanned. You’re looking for “ultimate-member”. Selecting only “ultimate-member” reduces the performance impact.
5/ Now open your website and navigate to the pages where the text is that you want to translate. In my case I needed to load the page where I had a member directory shortcode and a filter that used a custom field.
6/ Once you’re done return to step (3) and uncheck the checkbox.
7/ Refresh the String Translation page.
8/You can now either search for the strings you want translated or select “ultimate-member” from the “Select strings within domain” dropdown menu. I have 2 ultimate-member options in the list for some reason. My new strings appeared under the option with the highest number. Eg. “ultimate-member (1814)”
9/ Translate your new strings and you should be good to go.

This method seems to apply to other plugins too.

These steps are from the following post:
https://wpml.org/forums/topic/ultimate-member-directory-confused-in-what-field-label-to-pull-with-same-meta-ke-2/#post-5157161

However, I did not need to edit the Ultimate Member plugin as suggested.

In the case of the organiser the issue relates to this section of the new event form:

<div id="event_tribe_organizer" class="tribe-section tribe-section-organizer ui-sortable tribe-is-creating-linked-post">
...</div>

Selecting an organiser from the dropdown menu makes the follow fields visible, but they are all blank.

<input id="organizer-phone" type="text" name="organizer[Phone][]" class="organizer-phone" size="25" value="">
<input id="organizer-website" type="text" name="organizer[Website][]" class="organizer-website" size="25" value="">
<input id="organizer-email" type="text" name="organizer[Email][]" class="organizer-email" size="25" value="">

If you try and add an organiser with the same details you get the error that the organiser already exists – which is to be expected.

If the event is saved and the added event is viewed in the list, all the fields are correct, except for the organiser which has a dash ‘-‘. As explained previously this can be corrected by logging in as admin and updating the event on the backend.

This behaviour differs when being logged in as admin and adding a new event on the same frontend page. When an organiser is selected “Edit Organiser” appears next to the dropdown menu.