Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'change buddypress menu'

Viewing 15 results - 501 through 515 (of 515 total)
  • Author
    Search Results
  • #41992

    In reply to: Changing blog avatars?

    Lance Willett
    Participant

    Take a look at your admin menus for BuddyPress and Site Admin.

    If you are running an older version of BuddyPress (before revision 1311) look in Site Admin -> BuddyPress. Otherwise the latest trunk has a new top-level menu called BuddyPress (look in General Settings).

    View an example of the avatar menu.

    And… this probably isn’t a support topic, right? ;)

    #41833
    Robert
    Participant

    In your theme look for header.php. There you can change the names of the links.

    For example:

    <?php _e( \’Blog\’, \’buddypress\’ ) ?>

    Change it to

    <?php _e( \’My Blog\’, \’buddypress\’ ) ?>

    Remember to change it in your members theme too.

    Note that this will only change the text not the actual link. So it will show [My Blog] but it will still go to yoursite.com/blog

    #40726

    In reply to: Drop down menu

    bbrian017
    Participant

    Well I downloaded this version three days ago!

    Has it changed since then?

    https://buddypress.org/download/

    #39165

    lol Oh Ren… haha!

    @brandtd, this is certainly possible. As a matter of fact, this should happen as default unless you change the width of the body or html elements themselves. This is because the “Buddy Bar” isn’t contained by anything that has a relative position attached to it.

    In bp-core/css/admin-bar.css – Try…

    #wp-admin-bar {
    position: absolute !important;
    top: 0 !important;
    left: 0 !important;
    width: 100% !important;
    z-index: 1001 !important;
    height: 26px !important;
    color: #fff !important;
    text-align: left !important;
    background:url(../images/admin_bar_back.gif) #818181 repeat-x !important;
    }

    @brian, duh I get what you’re saying now. If I can give some feedback about the Buddy Bar for a moment, I feel that it should be an all or nothing kind of deal. Either it’s always there for people to use, or it’s never there and people have to naturally find their profile area and do things from there. Toggling a whole new set of what are essentially just short-cuts and adjusting the entire layout of the screen, even if by 26px, provides for a moment of awkwardness from a user perspective. For the 3 seconds it takes for someone to think to themselves “Hey what’s that? Do I need it? What does it do? Oh gosh there’s tons of menus now? What is this stuff?”

    Now if you’ve used WordPress.com or signed up for a Gravatar before, then the bar idea isn’t new. But for what I consider the core crowd we’re catering to by using BuddyPress as a social networking platform, if it isn’t uniformly worked into the design of the site from the beginning, it only serves to confuse.

    Again, this is just my opinion. Not saying it’s right, and certainly not saying that there is a better way. Just saying… :)

    /rant

    Back on topic. In theory you could put a…

    <body>
    <?php if (is_user_logged_in()){ ?>
    <div id="buddy-bar-buffer"></div>
    <?php }?>

    In your header file, and attach the CSS to that, rather than to the body itself? That would then only show that buffer when the user is logged in, and once they are logged in, that buffer will push the body down (as styled by the CSS you will give it in your base.css).

    Does that make sense?

    #38566
    Burt Adsit
    Participant

    sgrunt, works like a charm for me! Thanks. Can you post this in trac for everybody please? Just those two changes to those elements.

    https://trac.buddypress.org/newticket

    #38529
    huh
    Member

    As far as I can see these can be changed in

    member-themes > buddypress-member > header.php

    Search for id=”nav” around line 39

    Would be good to have a language file for these elements.

    #35848
    Burt Adsit
    Participant

    Mike the idea is that if I want to change the function of a menu item, I have to replace the menu item with something of my own. I want to change “My Account” on the bar and add a new item underneath entitled: “I Owe Mike How Much!?”. I have to replace the entire “My Account” menu item since the granularity of the actions are at the top level menu item only.

    I can slide new menu items in between existing items easily but that’s the way it has to happen for drop down items.

    I create a plugin that runs in /mu-plugins since I want this to run all the time for all users on all blogs. It’ll get run every page load.

    An example is replacing the bp logo image in the bar. Same technique for other menu items. The item gets rendered through the function:

    bp_adminbar_logo() in bp-core-adminbar.php

    This function gets registered in mu by us telling mu about this function and when to trigger it:

    add_action( ‘bp-adminbar-logo’, ‘bp_adminbar_logo’ ) at the bottom of bp-core-adminbar.php

    To replace the logo with our own logo or do something completely diff like just use the word ‘Home’, whatever we unregister the existing fn, register our own that replaces the old fn and does something different. Like below:


    function oci_adminbar_logo() {
    global $bp;
    echo '<a href="' . $bp['root_domain'] . '"><img id="admin-bar-logo" src="' . apply_filters( 'bp_admin_bar_logo_src', site_url( MUPLUGINDIR . '/common-interest/images/oci_home.gif' ) ) . '" alt="' . apply_filters( 'bp_admin_bar_logo_alt_text', __( 'BuddyPress', 'buddypress' ) ) . '" /></a>';
    }

    remove_action('bp-adminbar-logo','bp_adminbar_logo');
    add_action('bp-adminbar-logo','oci_adminbar_logo');


    The above says “don’t pay any more attention to the function bp_adminbar_logo() when the action ‘bp-adminbar-logo’ occurs, pay attention to my oci_adminbar_logo() fn and do that instead.

    You have to replace the *entire* menu item with something of your own. Clearer? No?

    nicolagreco
    Participant

    Here the solution, change this lines http://buddypressdev.org/forums/topic.php?id=15#post-58

    or Download the new 0.91 version

    #35434

    In reply to: Rename Wire Link

    David Bisset
    Participant

    I honestly don’t know where all the instances for this is (plus “wire” appears in the urls, etc.). First start would be checking out the bp_wire_setup_nav function in bp-wire.php file in mu-plugins.php. That at least would change the menu names. Then I would imagine you would have change text in the BuddyPress user themes…

    #35075
    Burt Adsit
    Participant

    Hi wardeh. I was checking the ‘topics with no replies’ and saw you here. All by your lonesome self. How goes the battle this week?

    You don’t want to turn off groups but you just don’t want the option to create more groups to be available. Well, you want group creation to be a site admin thing only. Hmmm…

    I went and looked at the member theme code and finally arrived in the core code and lo and behold Andy was thinking of you! There is an unused option for the menu items. ‘site admin’ only. You’ll have to modify one line to turn off the group creation option for everyone except you.

    In the file /mu-plugins/bp-groups.php at line 205. This currently reads:

    bp_core_add_subnav_item( $bp, 'create', __('Create a Group', 'buddypress'), $groups_link, 'groups_screen_create_group', false, bp_is_home() );

    Change that line to read:

    bp_core_add_subnav_item( $bp, 'create', __('Create a Group', 'buddypress'), $groups_link, 'groups_screen_create_group', false, bp_is_home(), true );

    That change adds the ‘true’ parameter at the end which normally defaults to ‘false’. It’s the ‘site admin only’ sees this menu item flag.

    Merry Christmas. :)

    #35061
    David Bisset
    Participant

    UPDATE: This trumps the first version of bp-test mentioned above.

    Basically I have created three versions of bp-test which allows one to learn and hopefully start building BP components. Here is a blog post with screencaps:

    http://www.davidbisset.com/2008/12/25/buddypress-building-your-own-components-with-these-building-blocks/

    For those impatient, here are the links:

    http://www.davidbisset.com/wp-content/uploads/2008/12/bp-testv0-1-0.zip

    http://www.davidbisset.com/wp-content/uploads/2008/12/bp-testv0-1-1.zip

    http://www.davidbisset.com/wp-content/uploads/2008/12/bp-testv0-1-2.zip

    Version 0.1.0:

    This version is very close to the proof of concept screenshots for Twitter and Friendfeed. Very basic – it just adds a menu and two submenus to that menu. It should automatically also add the menu to the “BuddyPress Bar” that appears at the top and (by default) is grey.

    Version 0.1.1:

    This version adds the “header tab” navigation you see in the screenshot on my blog. This requires a few additional PHP functions, and therefore increases the complexity a little bit. I also added a few BuddyPress PHP functions in the sample page that you should become familiar with but are very straightforward. This version rounds out how to create major navigational elements in BuddyPress.

    Version 0.1.2:

    This (final?) version changes the “Second Page” into an example of showing rowed results (similar to what you see on the wire page). This bumps up the complexity a bit since we use alot more PHP functions, mostly stored in the bp-test-templatetags.php file. We also use several classes seen in bp-test-classes.php and bp-test-templatetags.php. Also add a “standard” (of sorts) filter file (bp-test-filters.php). If you are planning on displaying anything in a table/row format like in the screenshot above, then you will want to examine this version. I have removed AJAX references to make it easier. Honestly this is all very close to the WIRE BuddyPress component so if you want to look at that as well, especially if you have the hang of this and just need to add in AJAX, that would be a wise move.

    These three versions support potential BuddyPress components ranging from the very simple to more-or-less the level of some of the current BuddyPress beta components. These building blocks will hopefully be a learning tool first (if you don’t understand what they do, then you won’t get very far) and a time saver second.

    #34749

    In reply to: Custom CSS & Groups

    Burt Adsit
    Participant

    Mike: if you are gonna mod the adminbar may I suggest this? A plugin that does the work for you without modifying the admin bar code. Andy made some changes to the adminbar to make it possible to replace menu entries easily and add new menu items between existing menu options. I use a plugin to do this. Used to modify it every time a change came thru SVN and got tired of that.

    Here’s what I use:

    http://pastie.org/344208

    That’s a link to the code for a little plugin I use. What that does is it adds a new top level menu item ‘Community’ with the News, Members and all the other items that are available in the home and member themes as buttons.

    You’ll need to modify this for your needs but it’s an example of how to add a new top level menu item and all the drop downs. The function oci_get_community_blog_url() goes out and gets some site options I have installed in my root blog theme. I don’t run the home theme on the mu root blog. I run it on community.ourcommoninterest.org. That menu gives access to the ‘community’ directories and recent activity. All the bp home theme stuff.

    More on the adminbar in this ticket: https://trac.buddypress.org/ticket/174

    #33860

    In reply to: Translating BuddyPress

    Dreamcolor
    Participant

    Step 1: Upload a MU language file to active the language select menu in “Site Admin” – “Options” page. This will make you can select sitewide default language.

    Step 2: Upload a BP language file. And its language will been changed with MU at same time.

    For example: I uploaded a file named “zh_CN.mo” for MU in “wp-content/languages/”. And now, In “Site Admin” – “Options” it will display a languages select menu. And in “Setting” – “General” will too. Now,I can change sitewide language or my own site language.

    At this time, if I want to change BP’s language, I just need to upload a file “buddypress-zh_CN.mo” file in “wp-content/mu-plugins/bp-languages”.

    You can test on my site, And I already translated BP and MU to chinese.

    http://dcote.net/

    PS: This is just a test site. So DO NOT post any importent things.

    #33412
    Andrea Rennick
    Participant

    I am not 100% sure that the download offers the home theme – yet.

    Go to the Site Admin menu, pick Themes and make sure the BP theme is the only one enabled. Then users can’t change themes.

    Any plugin you put in the mu-plugins folder does NOT show up on the Plugins menu. That is for plugins that are in the plugins folder. So no, you won’t see any BP related plugins there to to turn them off and on, because in the mu-plugins folder, plugins are always ON.

    If you really want to understand how WPMU works, to take full advantge of what it can do and get a feel for what you’re in for, check out http://wpmututorials.com , or sign up at wordpress.com to check out the user’s perspective & compare it to testbp.org.

    #33186
    Andy Peatling
    Keymaster

    So here’s why blogs are separate from home bases:

    BuddyPress is designed to support existing blog networks, as well as brand new installations. On an existing installation, users already have their blogs set up and established. Forcing a new blog on them just to use BuddyPress features would make no sense and most of them would be left empty and unused.

    It could be possible to give users an option whether or not to set up a personal blog with their new home base. The trouble is, that would mean some home bases have blogs, others not. That could end up being even more confusing for users.

    Also, another big problem is adding additional authors to the blog. This would mean other site members would be posting within a users home base which would mean an additional layer of security would be needed so they couldn’t access the main user’s messages, profile etc.

    Overall, separating blogs from home bases saves a whole lot of headaches, and allows BuddyPress to easily support new and existing installs. Perhaps we can work out a way to automatically set up a redirection from “user.domain.com/blogs/blogname/” to “blogname.domain.com” for each new blog. Going any further than a simple redirect would be fundamentally change the way WordPress MU works – and that’s not something we want to do.

    I’d also like to create a BuddyPress blog theme, that will tie in with the overall look and feel, and add the user navigation menu. This should reduce the contrast between home bases and blogs even further.

    Hope this explains the choice a bit more.

    Cheers,

    Andy

Viewing 15 results - 501 through 515 (of 515 total)
Skip to toolbar