Forum Replies Created
Also, words like “Help!” or “URGENT” don’t actually make anyone help you sooner than anyone else around here. Most volunteers will jump in and help who they can, when they can, — if you appear manic, it decreases the investment someone is willing to make in you, your site, and your topic.
Hoping to not sound discouraging. We’re excited you’re using BuddyPress, and want you to enjoy our community to its fullest.
You’ll need to be much more specific for anyone to help you.
You should never modify BuddyPress’s files. There’s no way for anyone to know what you’re doing to them, meaning there’s nothing we can do to help you besides recommend rolling back to an unmodified installation.
You should do what the error message says, and start by looking in your bp-core-avatars.php file, around line 1032.
If your site is live, and it’s critical to your users that it remain that way, it’s best not to modify live files on a live server, as this is the likely outcome.
Still where it’s always been, in bp-core-buddybar.php. It’s included directly, so the only way you’re getting that error is if the file is incomplete, or was modified.
Link to this plugin? I don’t see it in the list right now.
You’ll have better luck troubleshooting what’s going on with emails than you will going backwards in versions.
- What do your server logs say?
- Do normal calls to wp_mail() still work?
- Do email notifications work?
- Do you have other plugins that touch email code installed? If so, try deactivating them.
Users with the `delete_users` capability will always see the screen. Try it with a normal user and you’ll notice the screen isn’t there anymore.
Since your site was compromised, and you are the resident expert with your configuration, we rely on you to fill in any gaps that you can.
If you get to the point where you’ve identified a clear and repeatable security issue with WordPress, BuddyPress, bbPress, or any other plugin, let is know by checking out the following page:
Thanks, and good luck.
It’s worth noting that in the past, BuddyPress created bbPress 1.1′s roles in the same global namespace as WordPress’s blog roles. This is suboptimal, as it requires a user to be EITHER an Author, or a Moderator, or an Editor, or a Member.
Most people will want an Editor to ALSO be a Moderator, or an Admin to ALSO be a Key Master.
bbPress 2.2 and beyond allow for a user to have multiple roles on sites (in a network) that have bbPress active on them. On other sites without bbPress active, users still have regular old roles.
You probably don’t want bbPress activated network wide, unless you’re confident you want forums on every single site in your network. (hint: unlikely)
If you’ve already network activated bbPress, and if for some reason bbPress’s roles are in each of those subsites, you have some cleaning up to do. bbPress 2.2 and beyond do not save roles in the database anymore, so bbPress’s roles won’t float into sites they don’t belong in.
Roles are per site, and each site can have their own plugins active. Plugins like BuddyPress can sometimes be Network activated. BuddyPress does not add roles anymore; it used to with BuddyPress Forums in 1.5 and before. If this is a site from before BuddyPress 1.7 betas and bbPress 2.3 betas, some of the role integration is more complicated than it needs to be, and it’s addressed in 1.7/2.3.
We’re moving away from database capabilities exactly because of the confusion you’re experiencing. There’s no proper UI to display roles and caps in a way that makes much sense. There are plugins out there that try to help, but in my experience many of them provide medium functionality with high complexity.
Basically, you’ll need to do some digging, figure out what’s wrong, which could be an unlimited combination of things based on your configuration and needs…
The ‘Smashing Magazine’ article is, unusually, not a particularly good one and is just paraphrasing various classic but old articles; it’s section on float containment is NOT best practise- in fact it’s bad practice and should not be followed.
It’s a good read, regardless. Help educate, instead of working for free.
If you add a float to the container element’s CSS, it should resize itself.
A good read about floats from Smashing Magazine.
Howdy y’all. This was a small bug introduced in BuddyPress 1.5, that is now fixed in trunk, and will come as part of 1.7. I’ll cross-post this to bbpress.org, since I know users there are having these issues also.
Known issue since forever ago, but we’ve never had a good consistent report on where it’s happening and how to duplicate it. Thanks everyone for the info, and for the trac ticket.
@jwf3773 – Howdy. I know you’re new here, and we’re happy to have you around, but… you’re doing it wrong.
Boone is a core BuddyPress developer, but his plugins aren’t indicative of the BuddyPress project as a whole. If you’re trying to get a hold of Boone, there are way better ways to do that than claiming the sky is falling everywhere.
Going to close this topic, since it’s unlikely to go very far from here. Hope you have a great rest of your stay here at BuddyPress.org.
Sounds like your role wasn’t being automatically set correctly here on buddypress.org. Both of your accounts are set correctly now, and I didn’t make any changes. This isn’t cookie or cache related, it’s bbPress (what powers our forums) not behaving the way it’s supposed to.
It’s not the first time I’ve heard of this, but it’s something I haven’t been able to duplicate with new accounts. If anyone else has this problem, and reads this, drop into #buddypress on Freenode/IRC, and ping user ‘jjj’ so I can look at your account in real time when it’s happening.
No one specifically deleted your contributions. Someone was kind enough to wipe the codex of content last night, and I asked for a restore from a few days ago to be done on the codex site’s data.
Basically, modemlooper spent a bunch of time organizing the codex data, and I’m inclined to let him start setting some rules around what he thinks future contributions look like. That said, we are free to experiment, and we won’t always agree on what’s best. What’s important is that proper feedback is given and we all have a general feeling of it being rewarding to contribute even when your ideas aren’t the popular ones.
Ask Boone, Ray, and Paul how different our perspectives can be; I think it’s what makes our team so well rounded and great for the project. /tangent
The majority of users will google and find the exact page. When nested, if something is move or renamed it will break links.
It shouldn’t. Canonical redirect should take care of most cases.
Awesome, but you can not use the BuddyPress logo in non-official applications.
+1 – would you please kindly remove the BuddyPress logo. We love it as much as you do, but this app isn’t officially endorsed by the BuddyPress project.
Sounds like you didn’t completely move all the files in.
Also, I deleted the full paths to your file server that you pasted; unless you want to make yourself vulnerable to attack, which I would advise against.
The old forum to group relationship can be sensitive. From the error message, my best guess is it being a server configuration issue, likely with rewrite rules, or .htaccess… But it could literally be anything.
This isn’t a security issue; it’s just using the function method incorrectly. It’s a warning because you have WP_DEBUG turned on. If you don’t want to see these warnings or aren’t confident what they mean, you’ll want to read up about PHP’s error reporting and how to interpret them.