BuddyPress.org

oEmbed is supported by BuddyPress but maybe the embed_oembed_html WP filter isn’t used?

Can you open a Trac ticket for this?

This one is already front end enabled and I would have thought the dev’s would maybe like to make this feature a part of their plugin?

https://wordpress.org/plugins/mass-messaging-in-buddypress/

I’ve not seen a plugin that will do that, the closest I have seen is Crowdmentions which allows you to send a public message to @friends, but that does not send an email, only an onsite notification.

https://wordpress.org/plugins/crowdmentions/

Maybe you could ask one of the Mass Messaging plugin developers to add this as a feature?

Thank you @tempsgranollers for the feedback.

It is always important to update WordPress to his latest version.

This rule is also valid for plugins and themes

https://codex.wordpress.org/Updating_WordPress

The two most common causes of this error are a corrupted .htaccess file and exceeding your server’s PHP memory limit.

The .htaccess file in your WordPress directory can become corrupted after you install a plugin or make another change to your WordPress site. All you need to do is create a new .htaccess file.

bp_xprofile_field_type_textarea_editor_args

https://codex.wordpress.org/Function_Reference/wp_editor

@cofindrs,

BuddyPress doesn’t handle likes. That’s 3rd party plugin territory.
If Super Socializer has a notification option for BP users who doesn’t work, the solution is on the plugin author side.

If you think you can get a BP notification because somebody liked a post with help of Super Socializer, and there is no BP specific option in the plugin, i guess it is not possible.

Would be great to see more details about your statement: (Heateor) say that it is an issue in BP. Can you share a link to the discussion ?

Did you asked yourself for this issue on their support ? Your name doesn’t appear.

Keep an eye on https://buddypress.trac.wordpress.org/ticket/7392

Hi @sand06

Assuming the file is uploaded (and handled) by WordPress, you will need to hook to wp_insert_post

https://codex.wordpress.org/Plugin_API/Action_Reference/wp_insert_post

$post and $update will be passed to your custom function. You can use those to check if the post is a new file upload (attachment).

Hi @rglennnall

WordPress uses Plupload for file uploads, so you may want to check out that:

https://github.com/moxiecode/plupload

Hi,

do you mean this plugin ? If it is the case, you have to ask the author directly.

Or if you only want to add some comment to a content you share, you can use this plugin. It is outdated but still working (i use it without trouble since years).

it could be possible that your host plan doesn’t allow you to use BP.
it could be possible that you shouldn’t use php 7.1, as BP is not completely ready to use this latest php version.

To get sure, create a php info file and upload it at the site root (same level as wordpress)
Once uploaded, go to your-site/phpinfo.php. There you will see all information i asked you about your install. Check them and report them here please.

If you have an access to a php config via your host admin interface, go there and try to set it to php 5.6 or 7 instead of 7.1

Yes, it is not recommended to use 3rd partys automated WP installation tools. It is also not recommended to use page builders. Such tools are rarely updated, correctly maintained and often bugy… For 1.5$/mounth you can’t expect the creme de la creme, even if talented marketers try to suggest you the opposite.

Just jumping back in on this one.

I’ve been developing a large & complex WP site (60+ CPTs using Pods & BP) for the past few months on PHP 7.1. I ran all PHP 7.1 RCs and so far the only issues I’ve seen are related to BP. I’m now at the point where I’ve had to disable BP to continue development on PHP 7.1 (I need nullable types and void returns from PHP 7.1) and ignore any BP features I have on my roadmap until it’s stable (I hope soon 🙂 )

I can’t report any issues with WP-core and PHP 7.1 that I’ve witnessed.

No trying to say that BP is crappy 🙂 – just a hint that the issue may be more likely to be on BP side (especially since it seems that BBPress had a similar issue which they’ve already fixed – see my link in previous post).

The other issue I’m seeing on PHP 7.1 seems to be related to enabling Opcache and BP – https://buddypress.trac.wordpress.org/ticket/7361

Hope that’s helpful 🙂

Okay. The story is that PHP 7.1 is supported by WordPress 4.7 (or newer). Likewise, BuddyPress will need at least that version, too.

We’re currently tracking some unit test failures in PHP 7.1 (see the very bottom of https://travis-ci.org/buddypress/BuddyPress), but we’ve not figured out if they are our bugs, or some bug in WordPress core. Likewise, this do_action issue might be a regression WordPress should fix instead of us (if we’re getting caught by this, I bet many other plugins are, too).

At any rate, I’m going to try to fix the unit tests once I get a PHP 7.1 box set up (hopefully this week), and then I’ll test the basics of BuddyPress, and see what other issues crop up, and fix or report them as necessary.

I think I’d wait a month or two to use PHP 7.1 with WordPress and BuddyPress in the wild, to be honest.

Thanks for finding that one.

I’m trying to get someone from the WordPress team to confirm some details on their PHP 7.1 support, and once I have that, I’ll reply here again.

Hi,

not sure that this plugin was made to run with a defined root blog.

If you have issues with settings, you better have to ask for help on their support, or at least, read the documentation.

localhost/wordpress/index.php/members/: this is wrong and shouldn’t be used – even if you think it is working. It is not and that’s why you get a 404

This path should be localhost/wordpress/members/ or even localhost/members/
You cannot have a slug to a file followed by a directory. This doesn’t work, never and nowhere.
index.php is a file
/ is a directory
members is a directory name

Your htaccess is wrong too (at least for a standard install). Read here.

Check your local server settings first and reinstall correctly WordPress.
They’re hundreds of tutorials on the web. Select a recent one (> 2015) and follow the instructions.

If you are using latest WordPres (4.7). Then use custom WP-API endpoint to post content from cross domain. https://developer.wordpress.org/rest-api/

You will have to authenticate somehow, preferably oauth. https://wordpress.org/plugins/rest-api-oauth1/

https://v2.wp-api.org
https://oauth1.wp-api.org

I mentionned “groups” because you asked about forum – usually bp+forum is group forum…

What have you entered as site url in WP settings and what do you have in htaccess file ?
Did you enabled pretty permalinks ?
What is the permalink of your members page ? (the one under the page title, when you’re on the WordPress page editor screen)

Check your forum settings and sync WP and BP users.

Usually on a local site, and standard setup, while you use BP group forum, the forum slug is:
http://localhost/groups/group_name/forum/
If you use wampp, you should have a list of virtual hosts (aka site names), where you installed wordpress. This means also that wp is at the site root. If your site is called mario, you install wp there and then you should have http://mario/ Once BP is activated, you’ll get http://mario/members/ or http://mario/groups/ and so on…

The link to the forum user/author/commenter is
http://localhost/members/member_name/

When you use bbPress as standalone forum (aside or without BuddyPress), the link looks like

http://localhost/root_forum/single_forum/forum_name/
Link to user is the same as the one indicated previously.

More details here

Installing Group and Sitewide Forums

You can also follow the bbPress install guide if you use bbPress separately.