BuddyPress.org

BuddyPress does not provide a media directory, never has. My best guess, is that your theme has an integration with a media plugin, probably rtMedia, and if you install the right one, you’ll get options to make your own galleries. but it still would not include your activity post media in there as BuddyPress is in control of those items.

Hi there,

BuddyPress does not use the WordPress media directory, it uses it’s own directories for storing media

I Know this is old (but probably not by BuddyPress standards!) but this is actually an API issue: the WP heartbeat API has to be switched on for the frontend.

My host is Sitegrounnd and they dish out their own optimising plugin which has been responsible for a couple of things not working actually, this is one of them.

Under the environment tab is the heartbeat setting. It was switched off by default for the frontend for site performance reasons.

Find that setting!

I Know this is old (but probably not by BuddyPress standards!) but @Heather – brilliant this is it! My host is Sitegrounnd and they dish out their own optimising plugin which has been responsible for a couple of things not working actually, this is one of them. Under the environment tab is the heartbeat setting! funnily enough though I had it turn it on!

Switching to a new platform like BuddyPress can be a great way to improve your website’s user interface and experience, but it is important to make sure the transition is as smooth as possible to avoid any negative impact on your website’s traffic and ranking. Here are some steps you can take to make sure the migration process goes smoothly:

Back up your website: Before making any major changes to your website, it is important to back up all of your content and data. This will ensure that you have a copy of your website in case anything goes wrong during the migration process.

Choose a reliable migration tool: There are many migration tools available that can help you transfer your website’s content from WordPress to BuddyPress. Look for a tool that is reliable, easy to use, and has good reviews from other users.

Test the migration tool: Before migrating your entire website, it is a good idea to test the migration tool on a small portion of your content. This will help you identify any issues or errors that may occur during the migration process.

Customize your BuddyPress theme: Once you have migrated your content to BuddyPress, you will need to customize your theme to match the look and feel of your original website. This may involve tweaking the layout, color scheme, fonts, and other design elements to create a cohesive and user-friendly interface.

Test your new website: Once you have customized your BuddyPress theme, it is important to test your new website to make sure everything is working properly. Check for broken links, missing images, and other issues that may affect your website’s user experience.

Redirect your old URLs: If you have changed the URLs of your website’s pages during the migration process, it is important to set up redirects to ensure that users are directed to the correct pages. This will help maintain your website’s traffic and ranking.

Overall, switching to a new platform like BuddyPress can be a great way to improve your website’s user experience, but it is important to approach the migration process carefully to avoid any negative impact on your website’s traffic and ranking. By following these steps and being diligent in your testing and customization, you can ensure a smooth transition and a successful launch of your new website.

Same issue as well.
I have this error in console on click Send Reply
buddypress-messages.min.js?ver=11.1.0:1 Uncaught TypeError: e.has is not a function
at n.sendReply (buddypress-messages.min.js?ver=11.1.0:1:22353)
at HTMLDivElement.dispatch (jquery.min.js?ver=3.6.1:2:43064)
at y.handle (jquery.min.js?ver=3.6.1:2:41048)

sendReply: function(e) {
e.preventDefault(),
!0 !== this.reply.get(“sending”) && ((e = this.options.thread).has(“id”) || (e = this.options.collection.at(0)),
this.reply.set({
thread_id: e.get(“id”),
content: tinyMCE.activeEditor.getContent(),
sending: !0
}),