Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BuddyPress support #153

Open
4 tasks
slaFFik opened this issue May 24, 2017 · 3 comments
Open
4 tasks

BuddyPress support #153

slaFFik opened this issue May 24, 2017 · 3 comments

Comments

@slaFFik
Copy link

slaFFik commented May 24, 2017

  • Activity updates/comments
  • private messages
  • groups forum topics/posts
  • groups (they have title and description)
@websupporter
Copy link
Contributor

Hi @slaFFik,
thanks for this issue. Currently we are planning a general rewrite of Antispam Bee to have it more flexible. For me, one goal of this rewrite would be to have a set of Checks, which could also be used by other plugins, to validate spam e.g. for BuddyPress or CF7 in a smooth way. See for example #36.

This way, we could keep Antispam Bee quite easy to handle and still offer tools for example for a "Antispam Bee for BuddyPress"-Plugin.

What do you think about this thought?

@slaFFik
Copy link
Author

slaFFik commented May 24, 2017

This approach makes sense. So first the general rewrite should be completed.
Hopefully someone will write a BuddyPress connector after that :)

@Mamaduka
Copy link

@slaFFik waiting for general rewrite as well and will write BP connector.

@krafit krafit added this to the Future Release milestone Apr 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants