Background of the issue:
We have already told you about this problem before: https://wpml.org/forums/topic/the-gender-filter-does-not-work/ Regarding this issue, we spoke with WPLMS, and for them, it works through BuddyPress. BuddyPress stores the profile field values in tables. WPML stores the translated version of these values in a global string "file". WPML was never designed for filtering, and BuddyPress never anticipated that strings would need to be translated. Here is the response from WPLMS: "so our basic search goes like this --- $xprofile_query[] = array( 'field' => $filter['field_id'], 'value' => $filter['values'], 'compare' => 'IN', ); .... $args['xprofile_query'] = $xprofile_query; $args = apply_filters('vibebp_members_directory_args',$args); $run = bp_core_get_users($args); ---- now instead of values, we need to find the ID of the field value in the tables and use them. which would modify the default BP query as it only deals with field ID not their value ID. hidden link 3 fold changes, a. in the directory apis where we show filters we need to send ID values of the filter options. b. change the value to id in the directory script c. in the API we need to fix the BP query to include values from the selected filter options
This will make the option value "Gender" translatable with String Translation.
The only side effect, is that it will register a new string anytime you edit the option, instead of overwriting the already registered string, which means you need to manually clean up old strings on WPML > String Translation.
Take note, that prior to my provided workaround, which recently was escalated internally, it was not possible to translate the Gender Option in BuddyPress with WPML.
These snippets should register the strings for your Gender Option on String Translation and you might need to translate them again.
My apologies for the delay in answering, as I have been sick for a few days.
I would like to offer to have a closer look at the problem and request temporary access (wp-admin and FTP) to the website to investigate this issue further.
You can find the required fields below the comment section when you log in to leave the next reply. The information you provide is private, which means only you and I can see and access it.
IMPORTANT
Please be sure to make a backup copy of the website and database before allowing us access.
If you can't see the wp-admin / FTP fields, your post and website credentials are set as PUBLIC. DO NOT publish the data unless you see the required wp-admin / FTP fields.
I may have to install a plugin called "All In One WP Migration" to make a copy of the website where I can investigate the issue further.
However, I would also be very grateful if you could provide a staging site or copy of the website from your server yourself for this purpose. This step would only be required if the issue is replicable on such a staging site.
If you have any questions about creating such a staging site, you can consult your hosting provider. Just take note that WPML should be registered on this site again.
If you are unable to provide such a copy of the site for testing, please let me know on this ticket.
The private response form looks like this: hidden link
Next time you reply, click "I still need assistance."
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We may not access any access information not specifically submitted on this ticket in the private response form.
Indeed, until now the Gender Profile field was not considered to be translatable and our developers are still working on implementing this feature into a future version of BuddyPress Multilingual.
I see you are using on the page "App" the shortcode [vibebp_profile].
I see that this appears to be a WPMLMS related shortcode. I suppose this might be coming from the VibeBP plugin.
In this case this might be a compatibility issue between WPLMS/VibeBP and WPML and we would need to try to recreate this issue on a new test site and take further steps from there.
I would need your cooperation on this matter, as WPMLMS is a Premium Theme and we do not have a commercial lincense for it available.
hidden link
Further, as our compatilbity team stated here, the Theme is sold commercial as WPML compatible and the author handles the compatilbity for WPML in this case: https://wpml.org/plugin/wplms-2/
We can offer to have a closer look into the issue, but the final fix will need to be done inside the theme/plugin code by the theme author.
Let me know if you could provide the latest version of the WPMLMS theme and its plugin "VibeBP" for testing and I will send you a link to a WPML test site.
Thank you for not closing the ticket. We have asked WPML for permission to provide the latest version of the WPMLMS theme and its "VibeBP" plugin for testing and are still awaiting a response.
