Rodrigo Salles

Same here!

Hey guys, I THINK I’ve found a workaround for this problem.. All I needed to do was to change my callback function, adding a new “case null” into my switch statement and setup my function parameter to default = null ($country = null). In my case, I have 2 dropdowns, one for Country and another for Cities. Whenever the user changes the Country dropdown, my callback function returns a few cities for the selected country, something like:

function get_cities( $country = null ) {

	switch( $country ) {

		case 'Brazil' :
			$cities = array(
				"Curitiba" => "Curitiba",
				"São Paulo" => "São Paulo",
			);
			break;

		case 'USA' :
			$cities = array(
				"Chicago"  => "Chicago",
				"New York" => "New York",
			);
			break;
       
		case null :
			$user_id = um_profile_id();
			$user_city = get_user_meta( $user_id, 'city', true );
			$cities = array( $user_city => $user_city );
			break;

		default :
			$cities = array();
	}

	return $cities;
}

Basically, the problem is that there is a filter um_profile_field_filter_hook__select that’s resetting the value when displaying the field on the profile page (view mode). That happens because the plugin calls your callback function expecting it will get an array of choices (ie. cities) but it doesn’t pass the valeu of the parent field to the function.. o.O

So, if your callback function was like mine, with the default returning an empty array, this empty array was being returned to the filter, which was resetting the value of the variable used for displaying the field on the profile page.

Since this filter doesn’t pass any parameter to the callback function, I just setup the param $country to default to null, and then return the correct value of the field (city) in the array..

I am not sure what that could cause in other parts of the plugin, but it worked for me.. Hope that helps

/,,/

@timafeo @degami I am also facing the exact same problem. Any luck resolving this?

I really like the plugin but their documentation is really bad in terms of helping developers to build their own solutions.

I’ve seen that in my custom fields, too. Shouldn’t it be saved as empty string instead of “a:0:{}”?

Any fix for that?

thanks,