BuddyPress.org

Hi,
You are right about creating a home.php or front-page file and putting the content from activity/index.php

Here are a couple of things that I may suggest to improve it.
Since you are using the code (which is part of bp-legacy template and most theme include that), you activity/index.php does not have header/footer.
The easy way is.
1. copy the page.php from your theme and rename it to home.php
2. Now look for the section where you see the loop code( something like while(have_posts()) ..etc, replace only that section of code with the the content of actvity/index.php or you can put this line

<?php bp_get_template_part( 'activity/index' ); ?>

It will include the activity loop inside your home page.

You may want to look for the div/classes that is generated for your post. If you can inject that, it should look fine(as your theme supports bp and they should have the css.

If it does not work, please post the content of your homepage on pastebin and I will modify it for you 🙂

Hi @fptquangngai,

I am assuming you are referring to the name shown in the screenshot below:

This name you want to change is coming from the line bp_core_get_userlink( $user_id ); in the snippet you provided, which is part of the bp_message_get_recipient_tabs() function defined in the BuddyPress plugin under bp-members > admin > bp-members-functions.php.

It seems there are two things you can do here:

1. You can replace the bp_core_get_userlink() function in the message template (located at wp-content\plugins\buddypress\bp-templates\bp-legacy\buddypress\members\single\messages\compose.php) with your own custom function. See BuddyPress Codex for how to properly do this.

OR

2. Create a filter.

Since the bp_core_get_userlink() function uses the ‘bp_core_get_userlink’ filter for the returned value, you can hook into this filter and modify it in your theme’s functions.php file (or your own custom plugin). The only problem is that since the bp_core_get_userlink() function is used in other parts of the code (notably the BuddyPress Login Widget), you will have to make it so that the custom filter is used only under certain conditions.

Here is the custom filter I came up with. Its not refined, but serves as a working example:

add_filter( 'bp_core_get_userlink', 'my_bp_filter', 10, 2 );
function my_bp_filter( $string, $user_id ){  
    global $pagename;
    if ( isset( $_GET['r']) && $pagename === 'compose' ){
        $username = bp_core_get_username( $user_id );
        if ( $_GET['r'] === $username ) {
            $string = explode(' ', $string);
            $string = $string[0]. ' '. $string[1]. 'Alt="' . $username . '">'. $username . '</a>';
        }
    }
    return $string;
}

Hi @number_6,
Just wanted to post that it is easily doable with a small snippet of js.

Please put this code in your js file.

jQuery('#whats-new').off('focus');
jQuery('#whats-new').off('blur');

Please put this inside the document ready section for your theme’s js file( or please do let me know if you want me to provide the complete code).

By putting the above code, we have turned off the focus/blur events bound with the activity post box. So, There won’t be any fluctuation.

Now, we will need some css to make the activity box and the post button visible properly.

Here is the css code.

#whats-new-options{
height: 40px !important; /** I have used important to make sure that it will always be effective*/
}

form#whats-new-form textarea{
height: 50px !important;
}

hoping that the above code works for you. Please do post back it it works for you or not?

Hi,
It is easy to do that.
Here is a function, you can put it in your bp-custom.php or your theme’s functions.php

function devb_show_displayed_user_email() {
	
	if( ! bp_is_user() )
		return ;
	
	$user_email = bp_get_displayed_user_email();
	
	echo "<a href='mailto:{$user_email}'>{$user_email}</a>";
}

And you can call it on the user profile like this

<?php devb_show_displayed_user_email();?>

and It will show the email as links.

Hope that helps.

hi @mcpeanut,
Thank you.
I actually made a mistake by including the lighbox hurriedly. I am updating to have an option to disable it.

I have tested it on a few themes and it seems to have conflicts on couple of themes bacuse of my use of theme specific activity instead of supplying with the plugin.

I am looking on to improve it and I saw your suggestions yesterday there.

Please help me to improve it by providing your future suggestions here.
https://github.com/buddydev/mediapress

Let us improve it together 🙂
Thank you
Brajesh

I think you’re right in that bp-legacy files are used when a file doesn’t exist in your templates folder. In this case though I’m not sure the same applies as it’s a .js file. Perhaps @danbp will know what happens in this instance?

Update: After a little research, it seems as though the same does apply to .js files. See here which loosely mentions .js files

* As of BP 1.8 the paths for assets i.e styles and JS has been modified to look to your ‘buddypress’ or ‘community’ folders first…

So you’re right to think the JavaScript that expands the what’s new textarea on focus may exist elsewhere. But unless you’ve explicitly created the file in your theme, then bp-templates/bp-legacy/js/buddypress.js should be the only place.

On how it’s used for 2015, it’s not the name of a page, it the name of a document. And a document is a page content.

Feel free to use another theme. 😉

hi,

increasing the avaible memory means php memory, which handles scripts.
On a usual install, WP+BP need at least 128mo to run flawless.

Even if the server as the theoric resources, weird scripts or bad coded theme or plugins can lead to severe issues…

Read here for some basics about blank sreen of death.
This is actually the only issue which is real ! You have to consult the log files to track down the responsible script who generate this error.

Please give also more details about your install (theme name or site url, used plugins, server type and php, mysql version number) if you need more and/or better help.

Hi,

before asking for a fix, there is a need to identify the problem. You’re using 2 third parties plugin which you think are creating issues… Maybe, maybe not.

First of, give your site URL so other can try to help you eventually.
Second, if you’re sure one, or both plugins are defect somehow, you can ask on thei r respective support.

To be clear in regards of issues, ensure always that your base install is working correctly.
Is WP ok ? yes/no
Is BuddyPress ok ? yes/no
Is your theme ok ? yes/no

If 3 “yes”, each time you activate a plugin and something goes wrong, you’ll be sure it’s the plugin, and not your install. In 95% of cases, the culprit is the added extension.

This is a debug logic you can follow to find or try to, for explanations. 😉

I’m sorry too, but i can’t learn you to use BuddyPress and WordPress. I can only guide you. It’s a volonteer based forum, and understand that i can’t offer you a lot of my time.

You asked how to apply at least a background color to the buddy nav.

The CSS code i indicated should go in a file called style.css
This file exist in almost any theme. Open it and copy/paste the code, save and bam, you’re done.

For more explanation about child theme or any other custom work, you have to read WP & BP‘s codex or find some tutorials on the net.

Be also aware that you use a premium theme, which can be difficult for you to find assistance outside of the theme support.

Seems ok on my install.
Plugin tested on 2.2 RC2 and no “send message” button on my profile.

Problem is elsewhere i guess. Recheck your theme or custom code.

See bp-messages/bp-messages-template.php:1636

function bp_get_send_message_button() {
   // Note: 'bp_get_send_message_button' is a legacy filter. Use
   // 'bp_get_send_message_button_args' instead. See #4536

It’s intended so by default.

Try this from child-theme style.css
#buddypress div#item-nav div#object-nav ul li{background-color: #ccc;}

And which theme do you use ? Can you provide a site URL please ?

Congrats for your job ! 😉

I guess it’s not an error, but intended so.

Twenty Thirteen title on activity page:
your-site/activites/ activity | site name

Twenty Fifteen:
your-site/activites/ activities |

If on a user, profile the page title is the username – which is correct in regards of the h1 on that page: the username !

On previous Twenty themes, the title was username|blogname, not wrong but incorrect in regards of HTML spec. A page title should contain reference to a document. A blogname is not a document ! HTML5 title element.

<title> in this new theme is based on <h1>, without additionnal noise such as the blogname everywhere.

Did you also noticed that 2015’s header doesn’t contain wp_title() ?

For more about this new usage, see this ticket (nacin, yoast, boone,…)

The only thing i would change, is removing the pipe when an item comes alone or replacing it by a space. 😉

Visited your site, then uploaded wp framework to test it with 2.2 RC2 and got many php errors.
Immediatly after theme activation and a fatal error while trying to modify a group photo.

Seems you got it to work with 2.1.1, but as this theme was designed for BP 1.5/1.7′ BP Default, it’s most probably that some deprecated fonction are used by the framework.

I haven’t checked further, but imho, if you haven’t done special settings to use with 2.1.1, troubled times are awaiting you with next BP release.

WP Framework wasn’t updated since over 2 years, and BP 2.2 is very different of 1.7. They’re so many up to date frameworks on hand to play with, why do you choose an unmaintained theme ? 😉

@nunolopes99
I think your question is more related to the particular theme you are using. Which I believe has a support forum here: http://seventhqueen.com/support/

I am sure there are multiple ways to achieve what you are asking, but it would likely be customizing some php stuff or getting into plugins.. and I think you are asking more about the functions of the theme you have there. I doubt many if any here can provide you the the details about modding your theme settings for that one.

Oh i came across this issue in the past when trying out different themes, i cannot remember which theme it was that caused this for me but i did manage to solve it somehow but it was so long ago i just cannot remember, but it was definitely caused with a theme i tried and not buddypress, in the end i decided not to use that theme, so i would suggest finding a different theme first as @mercime said and if its the cause change to a diff theme unless you paid for it of course then make the issue known to the developer for a fix.

@lucdkny What theme are you using? Have you tried some basic troubleshooting like changing to the Twenty Fourteen/Fifteen theme?