[luccame]

@akukskuks

https://buddypress.org/support/topic/can-not-create-goups/#post-161399

[luccame]

Hey guys!

echo what? You do not have passwords of users to start with.

[luccame]

You both could be affected by this: https://buddypress.trac.wordpress.org/ticket/4834

If  the call to the_title() occurs outside the loop in your theme, BuddyPress fails to display the “Add New” button.

In this case you have to fix your theme.

Quick solution could be to create a custom template page for buddypress and relocate the call to the_title() inside the loop.

See: https://codex.buddypress.org/developer/theme-development/a-quick-look-at-1-7-theme-compatibility/

[luccame]

I noticed the same issue of sienteastu.

Found this on trac: https://buddypress.trac.wordpress.org/ticket/4252#comment:11

and also this: https://buddypress.trac.wordpress.org/ticket/2574

[luccame]

What theme are you using?

What version of BuddyPress?

See if this is your case: https://buddypress.trac.wordpress.org/ticket/4834

[luccame]

Under registration setting, choose the option that says “both sites and user account can be registered”.

[luccame]

I can see from the source of your site that you’re using WP 3.2.2
BuddyPress 1.6 requires at least WP version 3.4

[luccame]

Well done!

[luccame]

You should also visit http://bpdevel.wordpress.com/ where you can find information about dev chat sessions on IRC (next one will be Wednesday, 20th October – 19:00 UTC)
Please use https://trac.buddypress.org/ for bug reporting, this way your fixes have a chance of being applied to the core and released to the community.
Good luck with your project and thank you for choosing BuddyPress!

[luccame]

That’s an interesting implementation!

[luccame]

sounds interesting…. bump!

[luccame]

https://wordpress.org/extend/plugins/eventpress/download/

[luccame]

Yes indeed we may have seen a bit of slowing down recently, but IMHO: WP3 will be out this week and devs are really waiting for this final release. @johnjamesjacoby has worked on the 1.2 branch in the past few days and the trac says BP 1.2.5 is due in a couple of weeks, hopefully bringing even more compatibility with WP3 for the BP 1.2 branch. Then I think they will need to merge that with the trunk, where a lot of work is already done in terms of 1.3 roadmapped features. And what about the wonderful plugins coming within a couple of months from GSOC projects? And what about all the other plugin devs, constantly bringing us extraordinary new features for BP? Future seems bright to me!

[luccame]

This plan is as beautiful as aggressive, it really seems that you want to completely eradicate the problem, so I like it very much! Just add bold warnings to the user explaining that her account will be suspended if login/captcha fails too many times… real people deserve to be alerted.

[luccame]

This is almost my own case. Thank you for bringing up this important matter, I agree with your considerations.

[luccame]

I’m going to test it right now! thx Dave.

edit:

installed and activated sucessfully, it seems to work well.

to everyone:

remember to move “events” folder to your active theme (read the readme.txt file)

[luccame]

Nice plugin Peter, now even nicer thanks to categories and permissions management.

I look forward to see the exciting new features planned in your roadmap!

[luccame]

Nice plugin Peter, now even nicer thanks to categories and permissions management.

I look forward to see the exciting new features planned in your roadmap!

[luccame]

@r-a-y

I’d really like to see your RUO2 modification, I’d like to use it.

@paulhastings0

Tweetstream is going to have a brother… from the same great author, and it’s probably a matter of days…

[luccame]

I have the same problems of Dwenaus, similar configuration (WPMU 2.9.1.1 and BP trunk) running on a subdomain.

[luccame]

This is already planned on the Roadmap for version 1.4

[luccame]

https://buddypress.org/forums/topic/buddypress-editable-group-slugs

edit: sorry, not exactly what you need, but i’ll leave this for reference…

[luccame]

AFAIK BuddyPress uses that table to avoid running multiple query each time a page with activity stream is called. I also think that is limited to a maximum of n entries so it won’t explode…