BuddyPress.org

For a quick workaround, put the code below as line 577 in extension.php. Bump down the current line 577 to 578.

if($parent_id != 0) $params = array_merge( $params, array('per_page'=>100));

I think you’ll still see […]

Great! That should make things a lot cleaner. 🙂

Unfortunately, I can’t accept payment, as this plugin is being developed primarily for a JerseyConnect project. I appreciate the offer, though! 🙂

You should be able to restrict subgroups by setting each group so that “Nobody” can create subgroups. This is supposed to keep those groups out of the eligible parent group list and hide the “Create a Member Group” button […]

@jonnyauk: new version posted to the 1.3-compatible branch. Everything I’ve tested (routing, group creation, the tree) works on 1.3-bleeding, but I hesitate to release it until I can test against 1.2.x as well.

Have a look […]

@jonnyauk: I’ve been trying to fix bugs and lay the ground work, but haven’t had much time to work on improving 1.3 compatibility yet. Hopefully later today I can get started, and there’ll be something to show for it early […]

PS the site is looking great! I love the look and the nice front page!

@pnerger: thanks for the heads up! I think I’ve identified the issue, and a new release incorporating a fix will be out shortly.

Do you have short_open_tag = off in your php.ini file? I found a bug in the extension that MIGHT be causing this. A new version will be coming out shortly to fix that, and hopefully resolve this issue for you.

Hmm.. that’s an odd error. What versions of WP and BP are you running? Also, are there any other plugins active?

@pnerger: glad to hear it’s working for you 🙂

@johnnymestizo: I’m not on twitter, but you can email me any info to [my member name] at jerseyconnect dot net. I took a quick look at your site, and my first thought is that […]

That is not currently possible with this plugin.

I finally opened a trac ticket (https://buddypress.trac.wordpress.org/ticket/3312) so we can have a more focused discussion. Sorry for the delay. :/ @boonebgorges: I’d be happy to contribute code and/or experience to core developement! If the feature requests are any indication, there will be lots that people want out of the interface. @jonnyauk:…[Read more]

I do mean those checks. I think that’s what is responsible for the redirect.

And that is a really nice idea! That way the default constructor isn’t called if it’s not going to be used.

Unfortunately not. As soon as BP_Groups_Components sets up its globals, it also decides whether the path is valid. It will consider the child group name an invalid action variable and send a 404, so there’s no chance to go in and fix it after the fact. Using the bp_current_action filter (which is awesome, BTW) is […]

@djpaul: Thank you so much for the offer! I’m flattered that you’d consider altering the core to accommodate this. @jonnyauk, @djpaul: I’ve taken a look at 1.3 this morning and it’s possible to adapt hierarchy (at least the routing, which is the key) without any core changes. That being said, if there were a way to return a […]

Please provide any details you can about your setup: OS, web server, PHP versions, etc. Also, check your server’s error logs for any messages that might relate to this issue and include them. This will be very helpful in troubleshooting your issue.

Support for 1.3 is planned, but I haven’t even had time to look into it. Unfortuately, there isn’t a way around using the BP_GROUPS_SLUG. Calling the setup_globals function for the groups component, which appears to be where the constant is being defined in 1.3, sets off the built-in group routing process, which is not hierarchy-aware. […]

@mrjarbenne: Are you seeing any PHP errors, either on screen or in the server’s log file? I looked over the admin section of the extension, but there really isn’t anything that remarkable about it. Any error detail you could provide would be a huge help to troubleshooting this.

@pnerger: thanks for investigating this. I’ve got a workaround for the BP Group Extras issue, and a new release that incorporates it should be coming out shortly. If you want to get a head start, you can change line 549 in extension.php to: if(!isset($bp->groups->current_group->id) && !$params) { This should make the plugin more resilient to…[Read more]