BuddyPress.org

Greg’s an old client.

Sometimes we have room to troubleshoot stuff, sometimes we don’t. It’d basically be an hour consult.

@andrea_r

Gee, if that’s a service you offer, I’d be interested once I finally get my multisite project off the ground!

One of these days I’ll need to poke around your install (again) and see why they keep getting in.

I have it on my setup right now. I’m not sure that it’s doing anything for BP, to be honest, but I also don’t know how to check I looked at the plugin page on my wp-admin side and it’s all `./wp-comments-post.php` down the board.

Cookies for Comments works, though.

Thanks MikeyD. Don’t quite understand why he spammed the topic with my site however.

I am currently writing my own theme that looks nothing like BP-default, but I’ve been on trac almost daily with the UI tickets. I don’t know if we need a dedicated “UI/UX” team, but as long as folks are submitting on those tickets it will ease some of the other dev’s needing to mess with it. I DO think it is an important component with BP and we need to keep talking about 1.3’s problems.

I’m glad to see all the discussion going on, especially in light of all the “BP IS DEAD” nonsense. I think the biggest issue is how the forums make it hard to actually talk, but the testBP forums are great and I’m excited to see them go live here. I’m also anxious to see the new BP.org which seems to be slated to June.

My biggest issue with the BP sites I run is spam. Even my non indexed test servers get spammed. My AIGA site was deleting 250 spam users/blogs a day before shutting off new user registration. The first part of that comes from spam users being registered. There are two types of spam services, bots, and (slave) labor. These folks get through the Captcha’s and set up real fake accounts. But in my experience with my comment forms adding a Captcha killed a vast majority of spamers. Then with comments, contact forms, etc this would kill most spam. From there heuristic spam fighting from splogs, comments, etc. Also a system that users can mark a item as spam would help a ton.

Second, its that to learn how to do ANYTHING in BP I have to take something that works with the current version and hack it a part to figure out basic commands and actions. Once the new site is up I think there should be a real push on getting the Codex up to snuff(look at jQuery and WP) that have examples, resources, etc. Then have tutorials on things, hell syndicate them from other bloggers.

So as my thing(s) I want to keep being a part of fixing UI issues, and will as long as I can.
I want to write for the Codex, and am here and willing to write Blog articles for BP. Tutorials, Updates, whatever. I’m game. I will be writing tutorials for AIGA members anyway, so why not sync the content here.
I am working on the Group Documents plugin with its original developer because my sites need it.

And lastly I will be writing a BP-Spam component. I will do it as a plugin first and will want/need tons of feedback. But to get the University to sign off on my project I will need to stop all the Viagra and other inappropriate content from making it through. I will do this regardless of it being a part of BP but want to give back however I can.

I’m so psyched to see all the energy is still in this project!

What do you mean by deleted manually?

If you mark the account as a spammer, they can’t log in with that ID/email again. What’s the goal in deleting them?

2. for example ,if you set your profile as : just friends, then you have control of your activity stream and anything posted on your wall.
if your friends spam you, you just remove them from friends.
simple as that.
also users must have a option that allow them to mark as spam or delete spam. it works on FB.

1.better looking default theme( I’m willing to contribute a minimalist theme with an awesome option panel )
2.privacy settings( may help prevent spam )
3.activity stream on profile pages should have better order like (if I’m looking at my profile first thing I should see is my friends activity) also re-share on activity and post to wall as fb would be cool
4.forums not attached to groups

I also had this problem and went through a deep analysis.

The issue stems from the fact that Bluehost requires that the email be sent from an account that exists on the system. They do this as an anti-spam technique and they require this even if the mail is originating from within the system.

Enter WordPress. PHP uses a mail function mail(). WordPress maps this to wp_mail() and pretty much everyone uses the wp_mail for the plugins within WordPress. This makes sense as it allows customization of WordPress mail at a relatively low cost of performance.

Enter Buddypress. Buddypress places a filter upon wp_mail() such that all email originate from the user ‘noreply’ on the domain such that end users don’t reply to the notifications. Sounds cool.

But remember that Bluehost does not allow email to be sent from non-accounts and that’s the catch.

Using a foreign SMTP does not work for Bluehost blocks those ports. Using local SMTP will work but you need to provide the right setup and credentials. Finally, using mail-from plugin works since it filter’s the Buddyhost filter changing the email from address back to a valid Bluehost email account.

Hopefully, this explains what is happening and you can choose which strategy you want to use to fix the problem.

@psivait

re spam: I would do a little research as there have been some lengthy posts on this question /issue here so dig those up and give them a good read, there are plenty of steps you can implement to reduce spam, however be aware that there isn’t much you can do about human spammers and they account for a good deal of time wasting these days especially if you allow for blogs to be created at signup (something I don’t personally think a good idea).

As for approving multisite blogs as a single super_admin I’m not sure you can or should, multisite blogs are meant to be fully fledged blogs in their own right and the user that creates the blog is the admin. There are however steps you can take as the multisite admin to restrict what can be done on user blogs but that is more a question for WP than BP. If your meaning that you will have members on your primary blog that is running the multisite install and you want to elevate them above ‘Subscriber’ level to say ‘Contributor’ so they can post then that can be done and can and submissions will be ‘awaiting admin approval’ which you will see if you run through the options in the dashboard with perhaps a test user with a ‘Capability’ higher than ‘Subscriber’

Don’t add that , user Stacy – Stacey etc. is a fu..ing spammer giving the same advices everywhere , he only wants to harm your computer , it is a pity that on buddypress.org doesn’t exists banning or something like a forum moderation .

Username “Stacy” is a known spammer who gives “advice” that is potentially harmful to your computer. It is not advisable to use the code above.

This plugin should get you what you want:
https://buddypress.org/community/groups/buddypress-share-it/