Error on Accounts Page after adding profile picture

Simple fix if you don’t mind playing with PHP…
Fix it on line 928 by adding:
else { $disabled = ''; };

Thanks for reporting. Will pass onto lead developer to look at ??

Excellent. I’ve been having this error for a couple of months now as well on my registration page when WP_DEBUG set to true. The solution that bonzeny provided helped. Thank you.

To elaborate for anyone else having this issue, go to ultimate-member/core/um-fields.php and on line 926-928 you should see the following:

if ( $visibility == 'view' && $this->set_mode == 'register' ){
    $disabled = ' disabled="disabled" ';
}

Add the following lines of code right after:

else {
    $disabled = '';
}

If this is really all you need to fix this issue, then it would be worth adding this fix to the next update. I’ll mention this fix on the plugin’s GitHub.

You could always fix it yourself now rather than wait…

• Log in as admin
• Go to Plugins
• Find “Ultimate Member” and click “Edit” underneath the title
• find the file “ultimate-member/core/um-fields.php” in the right hand list of plugin files. (easy way to do this is use browsers find function…Apple-F on Mac or I guess Ctrl-F on PC…)
• scroll down or use browser search to find this code:

if ( $visibility == 'view' && $this->set_mode == 'register' ){
        $disabled = ' disabled="disabled" ';
}

• Easiest way to find it is using browser search of “$disabled”
• Once found add:

else { $disabled = ''; };

• Now should look like:

if ( $visibility == 'view' && $this->set_mode == 'register' ){
        $disabled = ' disabled="disabled" ';
} else { $disabled = ''; };

• Now click update file and then clear browser cache and check pages that had issue.

Yup, just updated my answer as you were writing that with the steps provides, thanks though.

As you know, it’s not recommended to edit the plugin’s core files since they could break things or get overwritten on the next update. Just hoping this quick fix will be included in the next update. for now, this will have to do.

Thanks for solving it bonzeny. I was trying to wrap my head around what was wrong on my end. Looks like the plugin has an issue when the field is empty in some cases.

haha yes I see that…whoops.

Also I totally agree with Ethan – the above is not recommended but is a temporary fix for those of you who know what they are doing and don’t want to wait on developers. But I strongly suggest on waiting if you’re not confident with editing PHP.

Hi All,

This has been fixed on the latest version of UM.

Thanks.

Thank you for the follow up and the fix.