xprofile_updated_profile actions pass different args

[nickmomrik]

When updating an extended profile from inside wp-admin, the xprofile_updated_profile action doesn't pass all of the args, namely the $old_values & $new_values which were fixed in #5755 for front-end profile updates. I took from that same code for the attached patch, also rearranging to match so visibility values could be passed in the old/new values as well.

[johnjamesjacoby]

Nice find!

Thanks for the patch. At a cursory, this looks good to me.

[dcavins]

Update the action 'xprofile_updated_profile' in BP_XProfile_User_Admin::user_admin_load() to pass the same parameters as the same action in xprofile_screen_edit_profile().

[dcavins]

Thanks for the patch! I've updated it slightly to adhere to comment styling and such.

For those just tuning in, the action xprofile_updated_profile() was called in two places:
BP_XProfile_User_Admin::user_admin_load() & xprofile_screen_edit_profile() with different passed parameters. The ticket author's fix is to harmonize the two functions, which is a great improvement.

[dcavins]

In 10822:

Harmonize parameters sent with xprofile_updated_profile action.

Update the action xprofile_updated_profile
in BP_XProfile_User_Admin::user_admin_load()
so that the same parameters are passed as
when the when the same action occurs in
xprofile_screen_edit_profile().

Fixes #7049.

Props nickmomrik.