BuddyPress.org

XProfile Fields in it, but only the full_name field is getting saved, all other fields are not getting saved when signup is complete.

Now, it is important the signup fields are registered in the proper location.

Confirm if your signup fields are correctly grouped here: https://bp-demo.test/wp-admin/users.php?page=bp-profile-setup In the Signup…[Read more]

Three things:

– I can’t replicate the issue you have.
– user_name is not a valid field, btw. It was deprecated.

Using the followwing payload, I actually get this in BuddyPress 14.0 since you are using + in the user_login, that’s not valid.

Request Payload.

`
curl -X POST “https://bp-demo.alley.test/wp-json/buddypress/v1/signup/”
-d…[Read more]

This was fixed and will be released as part of BuddyPress 14.1. https://buddypress.trac.wordpress.org/milestone/14.1.0

Can you share your BP Version, request payload?

We have a fix in progress: https://buddypress.trac.wordpress.org/ticket/9221

I see the problem, btw. But just trying to get more data about the BP version.

Can you share the error and which version of BuddyPress you are using?

Nice! I always wonder how many pizza restaurants are available in Frace. =P

Only if you want to. But it all depends where you have BuddyPress hosted. If you can get notifications when resetting a password, you can get send/recieve emails from BuddyPress too.

@hoopkonsulting As the error suggests, you are not sending a required field as part of the signup payload.

Before diving into technical or feature suggestions since as a developer I’m automatically wired to go via that route, I thought about asking non-technical people about the product, BuddyPress, itself.

I recently participated in the WordCamp US and had the chance of talking to a few people, besides conversations I had online (Slack, etc). I t…[Read more]

This requestion seems similar to this issue we got here: https://github.com/buddypress/BP-REST/issues/449#issuecomment-1196139043

> I’m able to use the provided function in that documentation article and get the proper response.

Awesome! Sorry for not seeing that at first. In my tests, I always get an array for bp_get_option( 'bp-active-components' ), so I did not see it as a possible bug at first.

Glad we sorted this out! =D

Could you also type cast this as an array? On line 98.

$active_components = apply_filters( 'bp_active_components', (array) bp_get_option( 'bp-active-components' ) );

I think this is coming as a string where it should be an array.

@wcholbi Odd! Could you var_dump the $active_components as suggested below?

var_dump( $active_components );
if ( 'optional' !== $type && ! empty( $components['core'] ) ) {
$active_components['core'] = '1';
}

@wcholbi Thank you for trying that again.

I’m still unable to replicate this issue but I think I know why that’s happening. Could you apply this patch and test it?

`
if ( ‘optional’ !== $type && ! empty( $components[‘core’] ) ) {
$active_components[‘core’] = ‘1’;
}
`

@wcholbi Could you share the error you are getting after applying my patch?

@wcholbi I’m able to replicate the issue and I have a fix for this here: https://github.com/buddypress/BP-REST/pull/450

Thanks for reporting the bug.

The activation key is necessary to avoid spam users in your community. It is an intergral part of BuddyPress and I wouldn’t recommend removing it.

The main reason to use the hook is in case another plugin or yourself try to reinstall the emails. If one does that, that email you showed creating will be deleted and you will have to recreate it by hand again. That doesn’t seem to be desireable.

Also, creating via the hook, you can use the correct name when sending the email. You say you read…[Read more]