Forum Replies Created
-
Not via the REST API.
You can use the activity endpoint: https://developer.buddypress.org/bp-rest-api/reference/activity/#list-activities
To get activities from a single group only.
@keithkhl Could you take a look at this comment here and provide testing steps?
@emanweb1 Can you share the request you are sending? Who’s logged in when performing this request? Is it a user? A regular user? An admin? Are you using an application password?
There is currently a ticket in progress: https://buddypress.trac.wordpress.org/ticket/8413
I created an issue here: https://github.com/buddypress/bp-activity-block-editor/issues/8
Also, the “security issues” as far as the ticket indicates, are not applicable to the version WordPress uses. Meaning that WordPress is updating to the versions without those issues.
I think Core should fix it first and then BuddyPress would inherit the update. Unlikely we will invest time into it since we plan to move things into the block editor.
@TheSupercargo I’m not sure if this is related to your problem and if you can test this pr.
We already have a ticket for this: https://buddypress.trac.wordpress.org/ticket/9044
I don’t think we force the emails to be sent as Plain Text. Can you confirm what’s the value for
wp_mail_content_type? Is it possible a plugin is hooking into this filter?Can you share that action you took? Also, a sample of the headers (you can hide the real information).
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:
your-site.com/wp-admin/users.php?page=bp-profile-setupIn the Signup Fields group.Three things:
– I can’t replicate the issue you have.
–user_nameis 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 theuser_login, that’s not valid.Request Payload.
curl -X POST "https://bp-demo.test/wp-json/buddypress/v1/signup/" \ -d "context=edit" \ -d "user_email=pratik@testmail.com" \ -d "user_login=testthe+request+" \ -d "password=\"']));L)Q542q8dL3" \ -d "signup_field_data[0][field_id]=1" \ -d "signup_field_data[0][value]=testthe+request+" \ -d "state=gggg" \ -d "country=AZE" \ -d "postal_code=444444" \ -d "mobile_phone=555555555"{ "code": "bp_rest_signup_validation_failed", "data": { "status": 500 }, "message": "Usernames can contain only letters, numbers, ., -, and @" }Here is the BP configuration I have locally, taken from my local site: https://bp-demo.test/wp-admin/site-health.php?tab=debug
version: 14.0.0 active_components: Extended Profiles, Settings, Friend Connections, Private Messages, Activity Streams, Notifications, User Groups, Site Directory, Members, Members Invitations url_parser: BP Rewrites API global_community_visibility: anyone template_pack: BuddyPress Nouveau 14.0.0 ! hide-loggedout-adminbar: Yes ! bp-disable-account-deletion: Yes ! bp-disable-avatar-uploads: Yes ! bp-disable-cover-image-uploads: Yes bp-enable-members-invitations: No bp-enable-membership-requests: No ! bp-disable-profile-sync: Yes ! bp_restrict_group_creation: Yes ! bp-disable-group-avatar-uploads: Yes ! bp-disable-group-cover-image-uploads: Yes ! bp-disable-group-activity-deletions: Yes ! bp-disable-blogforum-comments: No _bp_enable_heartbeat_refresh: YesThis 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 France. =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.
See the documentation.
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 think the overall feedback I gathered is that BuddyPress needs to find its product-market fit.
## Product-market Fit
The overall argument is that BuddyPress made sense when it was created because organizations needed a unique social network. Nowadays this is easily solvable with other tools that weren’t available at the time like Slack, Discord, Telegram, Facebook Groups, etc.
It’s much easier now to create social communities/networks using those tools than using BuddyPress. So as a project, we are not only competing against other open source projects but also with big companies which provide a solution to this problem in a much better way.
So far, all the conversation I’ve read about this issue sort of understands this new reality but the solutions presented miss this important point. So finding a new “place” for BuddyPress in this new scenario might actually be the most important thing we can do and that will define how we spend our resources going forward.
## BuddyPress’ problems
### Complexity
Before I became a BuddyPress contributor, I used to build small communities for clients. One of the first things I noticed about this niche was that all communities were the same but different. There was always a small tweak or a small feature on top of an existing component needed. BuddyPress was perfect for business. Clients didn’t know how to do it, so they hired me to build or extend it for them.
Even to this day, I still think BuddyPress suffers from this “problem”. If you are not a developer, BP is too hard to change. In BuddyPress’ marketing, it sells itself as flexible software, which is, but only if you are a developer extending or building something on top of it. Not to the regular users that install or try to use it.
I think this is an area where other tools thrive in comparison. People don’t usually build social networks with BuddyPress because it is open source. That also includes WordPress. They use WordPress because it is easy, a good solution for a problem at hand: “how do I make my own dam website?”.
Quoting feedback I got recently:
Every good product is a tool that helps people execute their creative vision, saves them time on boring tasks, or entertains in some way.
On top of that, BuddyPress is still considered expensive to many, be that due to the need to hire developers, to buy themes and plugins to accomplish their creative vision.
### Feature Set
I think BuddyPress has a strong foundation of features to create a social community. But as mentioned before, users are trying to execute this creative vision, so there is always something more needed.
This is an area where BuddyPress lacks as a project and in extensions (plugins that add features to BuddyPress) as well.
The most emblematic examples are the Follow Feature and the Media component. The first one because it is so basic in the land of social networks. And the latter in the lands of Instagram and photo apps. But the core BuddyPress plugin lacks both.
On top of that, features/components are pretty hard to integrate or extend as mentioned. Whereas other tools, provide an almost seamless experience, a rich set of features in a Jetpack-like style where you only need the click of a button to get something working and showing in the default theme.
### Conservatism
Here speaking as a contributor and observer of both WordPress and BuddyPress.
BuddyPress is still too conservative when it comes to changes or new features, however small they are. There seems to be a philosophy or approach that it’s practiced not against change but I’d argue that it is an almost “orthodoxical” concern to changes and new features which in my opinion is impeding the project to evolve.
A recent example was the introduction of PHPCS support which to me it would be considered a no-brainer but that it took more time to convince than I anticipated or expected.
And this is also an overall theme with BuddyPress. I see a willingness of the project to experiment and a desire to evolve but we still move at a very slow pace (even in the heyday of the project).
There is a “desire” to change and evolve but over years I also see a hesitation which “drags” the project a little bit.
### Low number of contributors
BuddyPress has been suffering from a low number of contributors in recent years. The reasons for that could be varied. It is also not clear if that’s actually a big problem for the project. I’d argue that it is not that big.
But it is clear that identifying what’s turning possible contributors away is a very good first step. And what we can do to revert that.
## Finally, some suggestions for the project
### Decide on a product market fit
This should have a high priority. Whatever we decide here will dictate how resources will be spent. What features will be built. What areas will have the most attention. IMO, this might be the most consequential decision for the future of the project.
### Improve the feature set
As mentioned previously, basic features of a social network are still missing in BuddyPress. Privacy, social networking, and following features are all missing. In the past, the argument I’ve always heard/read was that those features were better off served by plugins. Whereas users would be more likely to expect them inside the core plugin.
So I think BuddyPress needs a more complete set of social networking features. And that those features should be more integrated with each other and other parts of the site.
h3. Improve the project’s marketing
I think we need to do a better job of marketing what we offer. Not only look and feel but also of presenting information to the user.
–
That’s it! Not a lot of suggestions but I’m purposefully not adding technical suggestions to the project because I feel this is secondary. As long as we do not get into a new product market fit, we might not be addressing the real issue of the project.
=)
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
arrayforbp_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
stringwhere it should be anarray.
