[@k12onos Participant 12 years, 3 months ago]

I tested this out on fresh install of BP 1.6.1 and WP 3.4.2, and they seem to be working fine. But can anyone who upgraded from BP 1.6 + WP 3.4.1 provide feedback whether their site title is fine?

I tried to make the component pages not a child page, but it doesn’t work.. the page titles always show the component name and my site name (e.g. “Members | My site Name” ) on all the pages of that particular component.

I tried to use the BP default theme and deactivated other plugins too, but that doesn’t work either.. Can anyone help me? I really need to get the page title to work.

I really appreciate it if someone can help me or give some pointers on what might cause the problem. Thank you.

[@k12onos Participant 12 years, 3 months ago]

I’ve kept looking and looking but I can’t seem to find the code which produce a link to the latest post of a topic.

Can someone in BuddyPress team share what is used in this buddypress forum to link the timestamp to the latest post?

[@k12onos Participant 12 years, 3 months ago]

Thanks for the confirmation, meta caps in future releases will definitely make buddypress more powerful and customizable.

By the way, I found out on this site (http://shinephp.com/delete_users-wordpress-user-capability/) that on single site installs, wordpress checks whether user is a super admin or not based on the “delete_users” capability.

So, if anyone is planning to make someone be the admin of the buddypress, you can assign “delete_users” capability to that particular user (using your fav user role plugin).

Though, they will have access to (obviously) user deletion and some other plugin settings which checks for “is_super_admin”.

In my case it’s okay because the one I’m assigning the role to is a friend. I just don’t want them to have access to core/plugin/theme update&installs (is there anything else I should be concerned when indirectly assigning someone as super admin by the above method?).

[@k12onos Participant 12 years, 3 months ago]

I went through BP 1.6 code and stumbled upon the “bp_moderator” role in the code (though I didn’t see this in my wordpress & buddypress installation)

I also don’t see any other functions that checks back whether “bp_moderator” capability exist. Is this a planned role for future release?

[@k12onos Participant 12 years, 3 months ago]

I’m referring to the Group Forums (internal custom bbPress), not the sitewide one

[@k12onos Participant 12 years, 3 months ago]

I’m still trying to find a way to do this. But unfortunately I’m lost.. Let me know if anyone has even the slightest clue about this, then maybe I can get somewhere..

[@k12onos Participant 12 years, 4 months ago]

Anyone knows how to do this? I have an idea about where to edit the template file.. but I don’t know what code I should use to generate a link to the latest post..

[@k12onos Participant 12 years, 4 months ago]

Hi @Chouf1,

that actually works very well! Since now there isn’t any redirection the page loads without a redirection delay too. Thanks a lot for pointing that page out!

(Edit)

After using
`
define( ‘BP_GROUPS_DEFAULT_EXTENSION’, ‘forum’ );
`

I found this repeating over and over again in my error log:
`
[20-Aug-2012 18:56:13] PHP Warning: call_user_func_array(): First argument is expected to be a valid callback, ‘redirect_to_forum’ was given in /home2/public_html/wp-includes/plugin.php on line 484
`

I’m not sure what I should do now.. any clue?

Edit:

Sorry, this was caused by my silly mistake of forgetting to delete
`
add_action( ‘wp’, ‘redirect_to_forum’ );
`

[@k12onos Participant 12 years, 4 months ago]

I came up with this on WP 3.4.1 and BP 1.6:
`

function redirect_to_forum() {
global $bp;

$path = esc_url( $_SERVER );

$gpath = esc_url( bp_get_group_permalink( $bp->groups->current_group ));

if ( bp_is_group_home() && strpos( $path, $gpath ) === false ) {
bp_core_redirect( bp_get_group_permalink( $bp->groups->current_group ) . ‘/forum/’ );

}
}

add_action( ‘wp’, ‘redirect_to_forum’ );
`

I’m not sure whether this is an optimal/efficient code, I just wrote what works..

Is there anyone here that knows how to improve it? Does this redirect code burdens the server at all? I’m concerned with how the redirect will heighten the server load when multiple users open group pages. I’m on a shared hosting so this is something that needs to be considered..

[@k12onos Participant 12 years, 4 months ago]

Is there anyone experiencing the same or similar issue here?

[@k12onos Participant 12 years, 4 months ago]

Hi, I managed to recreate the problem on a new install.

This happens when commenting on updates of a private group in the activity stream. It does not affect hidden groups updates though.

Should I submit a bug report?

[@k12onos Participant 12 years, 4 months ago]

Hi, I disabled all my plugins but the same thing still happens.

BUT, I managed to find more information. This happens only on status updates on Private Group.

So is it possible that it’s something like, the BuddyPress didn’t check for the user’s permission when the ajax comment is posted, so when the comments are posted it is treated as “hidden/private” to the person posting it?

It’s a wild guess, but can someone with private groups & BuddyPress 1.6 help confirm this? I’m wondering if it’s just me or does it affect everyone.

[@k12onos Participant 12 years, 4 months ago]

@rodtrent

Throw out the idea of having a page structure like this:

Activity Stream (parent)
– Members
– Groups
– Forums

Instead, use a ‘dummy’ page or whatever you call it as the parent page:

Dummy page (parent)
– Activity Stream
– Members
– Groups
– Forums

The idea is to assign the dummy page with your desired base slug.

Though, you might notice that if you open the dummy page you’re left out with an empty page. Therefore if you want you can also redirect the dummy page to Activity Stream page so that the dummy page will be inaccessible.

At least at the moment, this is better than having to deal with the 404 pages right

[@k12onos Participant 12 years, 4 months ago]

@r-a-y

Hi, thanks for your reply.

Actually, this happened really fast. I was just a few hours on 1.5.7 when the new 1.6 update comes in. I can’t remember what exactly happened, but it is working in my local install of a WP 3.4.1 with BP 1.5.7. This is a mirror of what was upgraded into 1.6. Though I haven’t tried to recreate it on a new install because I don’t have the zip installer for 1.5.7.

But, the temporary fix that you mentioned works great, and it fits my initial purpose of having a “slug prefix/base” before the buddypress pages. Thank you for that