BuddyPress.org

Thanks @ubernaut. Yes, that’s a nice idea, but I do want to use site-wide forums.

The page structure is like this, but with more pages

Home
About
Community
-Forums
-Groups
-Activity
Contact

Anyway, I don’t think it’s going to be possible without some devine intervention :), as I noticed in testbp.org site, the ‘discussion’ menu is highlighted only when you select it (the page is forum-index). When you go any deeper (select a forum or a topic), the highlight get’s lost, so the issue is, the custom menu is not able to acquire/implement the hierarchy info, which may or may not have been provided by bbpress itself.

The same problem is there with the link you posted as well. On the other hand, all the buddypress menus and sub-menus and sub-sub-menus can correctly highlight the parent ‘community’ page. So, it’s a bbPress/forum specific issue.

Hi, I tried that prior to the above. Tried it again when I received your guidance. Didn’t work.
Any help is appreciated.

Can someone point me to the plugin used for the @ mention on buddypress.org shown below the person’s avatar?

uploaded wordpress 3,5.1 zip downloaded from wordpress. unzipped manually installed mysql installed buddypress with default buddypress theme manually created pages. contributor does not have add media. author does so will use author. thanks for your time i give up.

Hello all,

I solved the issue by using the hook `wpmu_activate_user`

Thanks for the tips 🙂

Hello,

I had created the paste of the code i had tried both in profile-loop.php and in

functions.php

`http://pastie.org/6050342`

The code is working fine in profile-loop.php but showing blank result in

functions.php

and now it seems the REPOST has disappeared, so here’s a better version:

Hi guys,
I just upgraded WP to latest version, and then after a long search found the CP 1.5 files and overwrote my 1.2.8 installation. Now to get it all working with my custom child theme Would love some help.

I’m trying to implement the article at https://codex.buddypress.org/developer/releases/developer-and-designer-information/, and

1) it says:

>>>>>>
You’ll also need to modify the following file in your WP theme:

/wp-content/themes/YOUR-THEME/members/single/home.php
Open up /members/single/home.php in your editor and add:

<<<<<<<>>>>>In your functions.php declare the function like this:

function bp_dtheme_enqueue_styles() {
// Bump this when changes are made to bust cache
$version = ’20110804′;

// Default CSS
wp_enqueue_style( ‘bp-default-main’, get_template_directory_uri() . ‘/_inc/css/default.css’, array(), $version );

// Right to left CSS
if ( is_rtl() )
wp_enqueue_style( ‘bp-default-main-rtl’, get_template_directory_uri() . ‘/_inc/css/default-rtl.css’, array( ‘bp-default-main’ ), $version );
}
add_action( ‘wp_enqueue_scripts’, ‘bp_dtheme_enqueue_styles’ );
<<<<<<

But then I get a "Call to undefined function add_action() " error

3) How do I ensure it will enqueue the .css file in my child theme directory?

4) Do I need to find the developer notes for upgrading to buddy press 1.4 and 1.5 as well and make other changes to my child theme? Where would I find these? The above link just talks about BP 1.5 and 1.5.2

5) I get undefined function error from my child them header calling

a) "bp_dtheme_page_on_front()" function.:

b) Call to undefined function bp_is_page()

It seems these functions aren’t deprecated, so how can i ensure they get loaded properly?

Thanks in advance

David

Makeshift solution posted here…
https://buddypress.org/support/topic/how-to-override-buddypress-function-using-hook/

I finally yielded, and messed up (so to speak) the function messages_screen_compose, adding conditional custom redirects with if else statements like…

`
if(wp_get_referer()){//to check origin of form submission, returns false for self submission
bp_core_redirect(wp_get_referer()); //custom redirect, as this isn’t self submission
} else {
bp_core_redirect( bp_loggedin_user_domain() . $bp->messages->slug . ‘/view/’ . $thread_id . ‘/’ );// this was originally there, for submission from original php file
}
`

As I think the issue is ‘resolved’, for time being, I should document the solution here.

I intended to use buddypress private messaging as feedback form, with various feedback options like Question, Suggestion, Feedback etc. Thus, I created corresponding users (Question, Suggestion, Feedback etc.) who will receive the feedback. The idea is super-elegant from my purpose, as not only the submissions be automatically segregated and stored in database, but responding to the feedbacks would be as simple as responding to PM, all without the hassle of email, spam etc. An added benifit is, users can draw attention to various issues site wide by @mension, like :@question What about this?”

So I tried to imitate the buddypress compose form, and I succeeded, except the redirect problem as described here.
https://buddypress.org/support/topic/create-a-feedback-form-using-buddypress-messaging-functionality/

What I was doing was, creating a duplicate form, but calling the original form action (fooling buddypress 🙂 ). I did so, because, I don’t even know how to submit the copy-pasted form I created, and get the same thing done as the original compose.php was doing when it called itself (self submission).

Anyways, this hack with unforgivable modifications in buddypress files works beautifully. I feel I’ll have to go through the plugin route finally though, as this is make-shift arrangement (but will work as long as I don’t update the buddypress plugin 🙂 ).

Thanks shane for your help.

Never mind, the $location refers to the url of the page where we will be redirected afterwords.

Will post back, If I ever get it done.

Thanks @shanebp. A couple of questions before I mark this thread resolved one way or other.

It seems a whole lot labour to write a plugin (which I’ll have to learn first 🙂 ) for a solitary redirect, but can I not do it in bp-custom.php, which seems to be for the same type of purposes, and conveniently resides in plugins directory?

Secondly, $location refers to the url of the page from which action originated as opposed to the location where the page will be redirected afterwards, right? I checked the referred wp codex page before I asked the earlier question, but couldn’t figure out what it meant.