suricate
Forum Replies Created
Viewing 2 replies - 1 through 2 (of 2 total)
-
Found another bug…
method um_remove_special_users_from_list filters user privacy settings. Problem: in line 66 where the query filter is built there’s a hardcoded “Yes”
array( 'key' => 'hide_in_members', 'value' => 'Yes', 'compare' => 'NOT LIKE' )When you’re using english as your plugin’s language you’re fine. Else this will fail because the setting is saved translated…
Fix:
add another query arg array containing the right value.$query_args['meta_query'][] = array( "relation" => "OR", array( 'key' => 'hide_in_members', 'value' => '', 'compare' => 'NOT EXISTS' ), array( 'key' => 'hide_in_members', 'value' => 'Ja', 'compare' => 'NOT LIKE' ) );Best solution would be to loop over all found translations and add the right query.
I did some research and found a fix.
file um-actions-profile.php
Edit line 64:
old:
$fields = unserialize( $args['custom_fields'] );new:
$fields = unserialize( $args['custom_fields'] ); $fields["profile_privacy"] = $args["profile_privacy"]; $fields["hide_in_members"] = $args["hide_in_members"];-> privacy fields are saved into database.
- This reply was modified 8 years, 8 months ago by suricate.
Viewing 2 replies - 1 through 2 (of 2 total)