Forum Replies Created
This was added in BuddyPress 2.6. See https://codex.buddypress.org/activity-embeds/.
dbDelta is a WordPress function, @danbp, it’s not bbPress specific. It’s used to update the schema of a MySQL database. The bigger question is how did something trigger the BuddyPress installation methods yet not make sure the relevant WordPress function was loaded.
@nhatnnt1 What version number of WordPress are you using?
You could also see if the user gets associated with the site they sign up on (this would be easiest to find out by looking at the Users screen in wp-admin for each multisite site, and seeing if/where users are listed).
I think with multisite, WordPress user registrations only occur on the main/root site. I don’t know how BP_ENABLE_MULTIBLOG works with this (i.e. I can’t remember if the registration redirect happens). It’s been a while since I’ve used it.
If you’re a little technical, you could test it, and then look in the database afterwards — probably the wp_x_users, wp_x_usermeta,
wp_x_signupstables, and see if there’s any field such as a blog ID or blog URL set somewhere for the new users that you could use.
Otherwise, I think you’d have to code something up.
Please do not at-mention people just to get attention. I normally stop reading if I see I’ve been pinged in a list like this by someone trying to get attention.
That said, thank you for your feedback.
All your Google image links are broken, and if they are screenshots asking “how can I do this”, if you can’t code (or want to spend time learning to do this), then you need to hope there’s a plugin out there you can buy, or hire a freelance developer to build it for you. Very few people build things for others for free, and it’s at a cost to those people, even if it’s free for you.
To comment on some of your points from my own perspective, and not on behalf of the entire BuddyPress team and all its contributors:
- I would also like to see better user communication management tools/preferences! (i.e. blocks). I think some of this will have to happen in the BuddyPress software, and some will happen in third-party plugins that extend the behaviour. There are already some plugins that deal with small parts of these areas.
- Chat, Message Attachments, Media — these are complicated, and I’m pretty sure will never be included in BuddyPress itself. They would make good third-party plugins. I think there are a couple of Chat plugins available already.
- (auto-)confirm accounts after sign-up — I believe this is seriously unsafe, so it will never be included in BuddyPress. Another plugin opportunity!
- Global search is something we always wanted, I don’t know if we still do. A very early BuddyPress default theme about 7 years ago had something similar, I think. I remember playing around with it. Maybe it’s time to bring it back. 🙂
- Sharing tools is pretty interesting. I think I’m personally quite keen to do some stuff like this, but it’d need some experimenting to see whether it felt as if it would fit into the BuddyPress software, or a third-party plugin, or some of both.
So… you CAN log into WordPress with your email address and password. On example.com/wp-login.php, it even says “Username or Email” and “Password”. Is this the main log in that you are talking about?
I have just tested the BuddyPress log in widget and I can log in using the email address.
I am a bit baffled why this doesn’t work for you. Please can you remove any relevant code customisations, and just test it again?
If you can’t log into /wp-login.php using an email address and password, you should try the WordPress.org support forums first and get that fixed, because that’s how it should be working.
You need to change a WordPress settings — you need to enable permalinks. Your WordPress blog URLs look like: example.com/index.php/roman-reigns/ and we need to have them look like example.com/romain-reigns/. This is required to have BuddyPress work.
If we’re lucky, you can go into wp-admin and Settings > Permalinks, then pick anything other than “Default”. Then save, and check if your blog post links have changed, and if they still work.
If they DON’T work, you need to fix that first. There is lots of information on the web about enabling WordPress permalinks, and if you have a good web host, oftentimes they will know how to enable them if they are disabled by default for some reason.
I guess that means that when a user registers on one of the multi-sites he can use his account on all the other websites of the Multi-site installation, right ?
Yes, but understand that you have to give that user access to those other sites (in wp-admin) to write blog posts, for example. If a user does not have explicit permissions to a specific multisite site, they won’t have any special access; they’ll only be able to read the content as if they were another normal visitor. You can test this right now, without BuddyPress, and see how it works.
meaning it takes him out of the French Website to put him onto the English on
You seem to be using multisite to have your content localised into different languages. This is a common approach for WordPress multisite, but BuddyPress does not work the way you want it to in this situation.
You can activate BuddyPress in a few different ways. Simply, on multisite, you can activate the plugin on a specific site, or network-wide. There is lots more detail at https://codex.buddypress.org/getting-started/installation-in-wordpress-multisite/ but if BuddyPress is activated network-wide, all the BuddyPress content will only appear on one site (we call this the “root blog”). We use redirects to support this, exactly as you’ve found.
You can’t have BuddyPress active on a multisite that uses the sub-sites as different languages, and have the BuddyPress social network appear on all of them and work in the same way, except with different translations. It doesn’t work that way out the box…
…however here is an advanced setting you can use to make BuddyPress behave like this: BP_ENABLE_MULTIBLOG
I would encourage you fully test this setting out if you enable it, before you start building the rest of your site, just to understand and confirm its behaviour.
@dioniq Did this work with a previous version of BuddyPress? If so, what version?
While the developers of that plugin are contributors to BuddyPress, you’re best to try requesting support via that plugin’s forums: https://wordpress.org/support/plugin/buddypress-docs
No, I’m afraid not. Nothing in BuddyPress has “trash”-like behaviour, allowing easy restores (to be honest, some of the extended profile stuff does but it’s a bit obscure to understand how that works). 🙁
You’d need to restore the appropriate data from the wp_BP_groups, wp_BP_groups_groupmeta, wp_BuddyPress_groups_members tables, from a database backup.
The code that @wmcomdesigns provided is PHP and intended to be used in a template.
@planetoffitness There is built in dynamic link support for member profiles. e.g. try
http://example.com/members/me/activity/mentions/on your site (changing the domain obviously) to redirect to the logged-in user’s activity mentions page.
Not out of the box, no. I don’t know if any plugins etc exist to do this.
I would strongly advise AGAINST remove KSES filters. It’s there for your protection.
Not via the UI. 🙁 But you can write some code! Add this to your functions.php file in your theme, it should work even if you add it on a newline at the very end of a file:
remove_action( 'admin_bar_menu', 'bp_members_admin_bar_notifications_menu', 90 );
@r083r7 Hi. You’re right that BuddyPress loads page.php as its default page wrapper template. The list near the top of https://codex.buddypress.org/themes/theme-compatibility-1-7/template-hierarchy/ shows the entire template hierarchy. Adding a buddypress.php file to your theme should have it load that template.
This file should be in the root of your theme, or inside a subfolder called “buddypress”.
I forget how setting the page template in the wp-admin page editor works with BuddyPress (I think @hnla and I fixed it at a WordCamp a few years ago). But the stuff already mentioned will probably take precedence over it.
If this doesn’t work, I’m not sure.
I saw the bug report you’ve filed, Dan, but I’ve not had time to look into it.
WP SEO plugins won’t work on those kind of BuddyPress “page”, because they actually are not real “pages”, so everything gets confused.
I’ve not seen a BuddyPress-specific SEO plugin – I suspect some people don’t realise they aren’t handled by most SEO plugins – or have been built with custom code.
In that case, you’re best off waiting until those users log in again, they’ll then show up.
(This error message in your screenshot refers to some other plugin, not BuddyPress. But anyway:)
To remove any plugin in WordPress, go into
wp-content/plugins/with FPT or however, and delete the plugin folder — in this case,
If you visit
your-site.com/wp-admin/plugins.phpdirectly, WordPress should disable the missing plugin.
If you happen to not be logged in, and so can’t get into
wp-adminbecause of the error… you could edit something in the database with SQL, but it sounds like you aren’t technically proficient with SQL to do this (it’s easy to break something else), so the last option — and this is a nuke — rename your theme folder to something else, rename the entire plugins folder to something else, then you should be able to log into wp-admin. WordPress will switch to one of the default twenty* themes. You can then rename the plugin folder back and start reactivating them one-by-one, and then switch the theme back.
Unfortunately there aren’t any management features built into WordPress to deal with uploaded user/group pictures (or cover images) in the same way that WordPress has its media library. This may change, but probably not for a long while, or until a contributor appears who really, really wants to fix this.
I wouldn’t worry about unused images on your server. If you’re worried about disk space, get a better host with more filesystem space. This shouldn’t be an issue nowadays.
If you don’t have dev resources to track it down and if the site isn’t on GitHub publicly or something, it’s going to be veeeeery difficult to come up with any meaningful suggestions where to look. I’m not sure where to start.
Exactly. The first thing you want to do @phound1 is verify if WordPress sends its own emails. An easy example is the comment moderation notification email. If it does not work, obviously fixing that is the first step. Let us know, we’ll try to point you in the right directions.