Replies
Thank you. I am looking forward to it.
Regards
BrajeshHi Jay,
Welcome to BuddyDev.I sincerely appreciate you for the concerns and interest in reporting the issue. I hope it is not related to shortcode as we fixed the issue and update was released last week.
Please drop us a line via our contact form
https://buddydev.com/contact/and we will get in touch quickly.
Thank you
BrajeshHi Avi,
Thank you for your question and your interest in the plugin.I am sorry, the plugin allows moderating XProfile data. User name is not part of xprofile data and can not be moderated by this.
Regards
Brajesh- Brajesh Singh on January 12, 2026 at 11:35 am in reply to: How to avoid the switch showing users on the members loop #55977
Hi Alex,
Thank you for the question.You are right, the bug is in the function
bp_nouveau_get_members_directory_nav_itemswhich usesbp_get_total_member_count.I will suggest reporting to the BuddyPress team as it is bug in the core.
Regards
Brajesh - Brajesh Singh on January 9, 2026 at 9:44 pm in reply to: How to Add a dropdown of values from repeater fields to activity post #55973
Hi,
I am sorry but your frustration is misplaced.
We are here to help with our plugin.– Did you mention in question that you are needing guidance/assistance with development? How would I know the question was from a developer?
– Where do xprofile custom field type offers repeater field? I am the developer and I am not aware. Please point me to the file/code.
I am sure you will figure out and you are on the right track. Profile fields are not for activity(unless you cache them, they will be very costly if used on activity stream).
If you need any specific pointer, Please feel free to ask.
Regards
Brajesh - Brajesh Singh on January 9, 2026 at 9:37 am in reply to: How to Add a dropdown of values from repeater fields to activity post #55970
Hi Lisa,
Thank you for the question.I am sorry, we do not have an answer to it.
The xprofile field types are for user profile and you will need a developer for any custom development(to add the fields to activity).
Regards
Brajesh You are welcome. It is always a pleasure to assist 🙂
Hi Gary,
Thank you for the post. We released security fix few days ago( Just for the information, we were informed about the issue and public disclosure was after the fix).Please upgrade from https://wordpress.org/plugins/bp-xprofile-custom-field-types/
Regards
BrajeshHi Alex,
Thank you for the reply.You have raised some real fair questions and concerns and I will address each of them.
1. Future of BuddyPress:-
Since 12.0, BuddyPress development has been going downhills. Fragmented eco-system, lack of developers(active), limited capability, old code base, these are the negatives. Unless the team decides to break away from their legacy/ecosystem, It is going to be really difficult to create positive experience with BuddyPress. BuddyPress was the first software for WordPress that allowed creating social network/community and that’s why it is still being used(the active installs have been falling sharply for last 5 years). Their architecture was good(modular)for that time but it has too many bottlenecks for the current era.BuddyBoss is affected by similar issues + Bulky code base. The good thing abut BuddyBoss is their User experience(UI/UX).
We wanted to avoid the past baggage. That provides us with huge advantage of building something from a new perspective and design the architecture as we see fit for today/future. It also helps us provide better user/developer experience.
We have been focused on low entry barrier/resistance and we hope to achieve that.
2. Why not fork BuddyPress:-
Forking will not help much as we will have the same issues that current BuddyPress/BuddyBoss suffers. Also, we will be stuck with the ecos system and create negative experience. Our goal is to create net positive experience for Site admins/Developers/Users and creating a new system from scratch is the best way to achieve it.3. What happen’s to our BuddyPress/BuddyBoss plugins:-
We will not develop any new plugins but we will keep updating and supporting all our plugins for atleast 3 years from now. After that, we will either put all code on github or let nanother developer/company acquire them.4. Will there be a way to migrate:-
Yes. We will be providing migration from BuddyPress, BuddyBoss a couple other plugins for migrating user/data.Many of the current features form our plugins/BuddyPress eco system are going to be in core. You may not need plugins. Search is part of core(still to be implemented). Most of the features from the current system will have better implementation available as art of core/extension.
It is not going to be a premium only plugin. After initial release and user feedback/updates, we plan to put the core on WordPeress.org and develop via github. It is a freemium model, not a paid only solution(Initial release is for paid users only).Regards
BrajeshPS:- Please open a new topic in future to keep the discussion focused on your actual query/concerns.
Hi George,
Tahnk you for the reply.I don’t think we have a competition here and we need to compare our goals with the project.
I understand your goal is to create a new experience and trust based network(what is trust? different people have different perspective on it and it is not the right forum to discuss it philosophically).We(BuddyDev) are not creating a social network, we are creating a software that allows site admins to create social network. What is that network and how it works is not our concern. We are not here to decide for site admins, our goal is to provide the tools and let the site admins decide what they want to do with it.
As of data ownership, unless your users are storing their data on their own systems, there is no real data ownership. The client server approach(where one or more servers store data) and not all users run their own server is not going to solve data ownership(Mastodon does allow users to run their own server, but users may be part of a server run by someone else too).
There are always going to be legal rules around world(Like EU/Australia’s current rules), and they are dynamic, they will change over time. Our goal is not to incorporate them into our software. Our goal is to enable site admins with tools to make the compliance simpler/easier. For that reason, our identity is not around these compliance, compliance is just one of the many things our system will provide easier tools/integrations.
As of your question:-
What is the architecture of this software
Client/server with partial inspiration from DDD.
Is your plan to use the existing user and security architecture of WordPress? I personally think that lack of granularity of access and trust levels meant BP was never scalable.
Yes, we are and we do not see any issue. WordPress provides granular role/capability based system which can be extended for all use cases. BuddyPress’s problem is not use of WordPress users, It is how they store/fetch data.
But also, WordPress is going to die soon. It’s moving commercial, this is why my ultimate goal is to have my mini servers hosted on peoples own PCs, and not need hosting, not from a hosting provider.
You are entitled to have your opinion. I have full faith in the future of WordPress and we are sticking with it. Also, you have all the rights to decide how you envision your software being used, for us, WordPress suits our requirement pretty well and we have full faith in the future potential of it.
To sum it up, we are creating a modern social network creation tool that will allow users(WordPress admins) to create social communities with various use case. Since our system is modular, It allows future extension without being limited by the current constraints. We are not re-inventing social networking(We believe the existing social networks like FB, X, LinkedIn, Reddit, Instagram etc.) is a good indicator of how a social network should work , we are rebuilding for a better experience and rapid development with WordPress.
Regards
Brajesh