BuddyPress.org

And you use the BuddyX theme with BuddyPress and not the BuddyBoss Platform right?

You can send me an email here: support@spiritualskill.com

This reply will be deleted once you reach out, in order to prevent spam mails in the future. 🙂

Re. avatar size, not sure, you can try putting a span around your shortcode, give it a class and with CSS try to force the avatar size.

Or you can add a class into the fetch_avatar array and try that way.

See: https://www.buddyboss.com/resources/reference/functions/bp_core_fetch_avatar/

Hello @varunkamani

I already gave you a few options to choose from, so in the end it’s up to you.

1. Ignore error and keep plugin
Keep the plugin and accept the fact that it comes with some issues and risks.
The risk itself is pretty low when it comes to the XSS since this is pretty common.
Like mentioned before, old and unsupported plugins do come with some risk.

2. Find a different plugin
Find a different plugin that is updated that can provide you with the features you need/want.
You can search on both WordPress.Org or other sites like Google, CodeCanyon etc.

https://wordpress.org/plugins/

3. Use a third party security plugin
Download and install a third party security plugin that can help prevent the XSS attacks on your site. This could be either free or paid/premium depending on your budget and needs.

4. Get a developer to help you update current plugin
If you insist on keeping the BuddyPress Global Search and you want it updated to fix its current issues, you’d need to pay a developer to help you update the plugin itself. This might not be the best solution long term, and I would also assume BuddyBoss themselves would update this if they felt it was necessary. The fact that they talked about updating it for the past 3 years and now left it abandoned tells me that it’s not a priority for them.

From a quick search on the forums, this topic has been up several times before for the past many years, so don’t expect an easy or “free” solution for this.

Hope it helps! 🙂

I’m no longer using BuddyPRess or bbPress. I switched to BuddyBoss and gave up on trying to get BuddyPress to work the way I wanted.

I think you have used BuddyPress and BuddyBoss themes. You can try deactivating the BuddyBoss theme temporarily to see if the issue persists, which will help determine whether the problem is related to the theme or BuddyPress itself.

Thank you, but after updating the plugin to the lattes version, a notification message is stacked at the top of my WordPress admin dashbored as follows:

(For BuddyPress Multilingual to work you must enable WPML together with BuddyPress or BuddyBoss.)

—————————————-

even the WPML and BuddyPres are already active and working

Buddyboss got sold to awesome motive. More competition for buddypress. We are currently at a declining rate sitting at 2016 levels.

We are not Buddyboss support

Think you’d need to ask BuddyBoss about that. BP does not interact with those pages, and presumably the login page is theirs also.

Elementor compatibility and a good documentation like BuddyBoss has.

Thanks for the response! I installed classic but no change.
No change when I de-activate the ‘Buddy Press for Learndash’ by BuddyBoss plugin. (https://wordpress.org/plugins/buddypress-learndash/)
I checked with LearnDash and this is still the plugin they advise to use – even though it hasn’t been updated in 4 years. We may just abandon the functionality – it doesn’t offer much value to us if it’s not connected to the online course. I suspect the BuddyBoss plugin is the issue.

Hi there, and welcome to the world of BuddyPress! Don’t worry; the 500 error can be daunting for beginners, but we’ll work together.
I’ve seen this issue reported before with the Lambda theme and BuddyPress, and it boils down to a compatibility issue with the navigation functions. Here’s how we can tackle it:

1. Debug Mode Explained:
Good job enabling debug mode! The error message you shared (“Call to a member function get_primary() on null”) points to line 2558 in bp-core-functions.php. This line attempts to access a navigation menu item that’s not available, causing the 500 error.

2. Don’t Modify Core Files:
While removing the problematic line might seem tempting, avoiding modifying core BuddyPress files directly is crucial. This can cause conflicts and instability down the line.

3. Theme Compatibility Fix:
Instead, let’s explore theme compatibility options:
Theme Update: Check if an updated version of Lambda is available. Developers often fix compatibility issues in newer versions.
Theme-Specific Navigation Hook: Some themes, like Lambda, provide custom hooks for modifying the navigation. Research Lambda’s documentation or contact their support team to see if such a hook exists. You can then use this hook to customize the BuddyPress navigation without touching core files.
Alternate Theme: Unfortunately, if compatibility solutions are unavailable, switching to a different theme that plays well with BuddyPress might be necessary. Popular choices include BuddyPress-compatible themes like BuddyBoss, BuddyPress Theme, and Total.

4. Community Resources:
Don’t hesitate to tap into the wider BuddyPress community for support:
BuddyPress Forums: Head over to the BuddyPress forums and search for similar issues related to Lambda and navigation. You might find existing solutions or helpful advice from other users.
BuddyPress Slack: Join the BuddyPress Slack community to chat with developers and experienced users in real-time.

5. Next Steps:
Based on your preference and technical comfort level, please choose one of the suggested solutions and try it out. If you need further assistance with specific configurations or troubleshooting, please share more details, and we can delve deeper together.
Remember, the BuddyPress community is friendly and supportive, so don’t hesitate to ask for help. Good luck, and I hope you get your BuddyPress site up and running smoothly soon!