Skip to:
Content

BuddyPress.org

Opened 5 years ago

Closed 5 years ago

#8174 closed defect (bug) (fixed)

Registration process is generating an error when the xProfile component is not active

Reported by: imath's profile imath Owned by: imath's profile imath
Milestone: 5.1.0 Priority: highest
Severity: critical Version: 5.0.0
Component: Registration Keywords: has-patch
Cc:

Description (last modified by imath)

How to reproduce :

  • Allow signups on the site
  • Deactivate the xProfile component
  • Fill the registration form on site.url/register
  • Validate > error because bp_xprofile_fullname_field_id() is not available

FYI this is a regression introduced in [12349]

Attachments (1)

8174.patch (2.3 KB) - added by imath 5 years ago.

Download all attachments as: .zip

Change History (5)

@imath
5 years ago

#1 @imath
5 years ago

  • Description modified (diff)

This ticket was mentioned in Slack in #buddypress by imath. View the logs.


5 years ago

#3 @imath
5 years ago

In 12503:

Make sure users can register when the xProfile component is not active

In version 5.0.0, we've introduced an improvement to use the display name as the salutation in signup emails (see [12349]). To do so we rely on an xProfile's component function. When this component is not active, the function is also not available causing a fatal error and preventing the activation email to be sent. To fix this issue we are now checking the component is active before using the function to return the display name.

See #8174 (Trunk)

#4 @imath
5 years ago

  • Owner set to imath
  • Resolution set to fixed
  • Status changed from new to closed

In 12504:

Make sure users can register when the xProfile component is not active

In version 5.0.0, we've introduced an improvement to use the display name as the salutation in signup emails (see [12349]). To do so we rely on an xProfile's component function. When this component is not active, the function is also not available causing a fatal error and preventing the activation email to be sent. To fix this issue we are now checking the component is active before using the function to return the display name.

Fixes #8174 (Branch 5.0)

Note: See TracTickets for help on using tickets.