Thank you. I am looking forward to it.

Regards
Brajesh

Hi 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

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

You are welcome. It is always a pleasure to assist 🙂

Hi 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
Brajesh

PS:- Please open a new topic in future to keep the discussion focused on your actual query/concerns.