Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'buddypress'

Viewing 25 results - 61,451 through 61,475 (of 69,046 total)
  • Author
    Search Results
  • #55217
    Jeff Sayre
    Participant

    Did you choose “Set up a new bbPress installation”” or “Use an existing bbPress installation”?

    If you do not need any of the old bbPress content, then I would suggest starting the bbPress integration from scratch. This mean deleting the old and newly-created bbPress tables in the DB, then deleting the bbPress directory from BuddyPress, and then reinstalling the bbPress files. This of course also assumes that the new bbP tables do not yet have any worthwhile data in them.

    Next, go back into WPMU’s backend and navigate to “BuddyPress > Forums Setup” and then choose “Set up a new bbPress installation”.

    Does that make a difference?

    #55216
    madyogi
    Participant

    Okay, so I followed your advice, toddlevy, but for whatever reason, I’m still getting my profile header the home page. The following is in my header.php file:

    <?php

    global $bp;

    if ($bp->current_component == BP_XPROFILE_SLUG) {
    include (TEMPLATEPATH . '/../ARHealthCareersFrameTheme/customHeaders/communityHeaderTest.php'); //include this header on BuddyPress profile pages
    } elseif ( is_home() ) {
    include (TEMPLATEPATH . '/../ARHealthCareersFrameTheme/customHeaders/homeHeader.php'); //include this header on home page
    } elseif ( is_single() ) {
    include (TEMPLATEPATH . '/../ARHealthCareersFrameTheme/customHeaders/homeHeader.php'); //include this header on posts
    } elseif ( is_page('Why We're Here') ) {
    include (TEMPLATEPATH . '/../ARHealthCareersFrameTheme/customHeaders/homeHeader.php'); //include this header on about page
    } else {
    include (TEMPLATEPATH . '/../ARHealthCareersFrameTheme/customHeaders/communityHeader.php'); //include this header on BuddyPress pages
    } ?>

    Any ideas as to why this would include communityHeaderTest.php on the home and about pages? Single pages are including the correct header.

    I have been working with this code in my header, which seems to work for what I need:

    <?php

    if ( is_home() ) {
    include (TEMPLATEPATH . '/../ARHealthCareersFrameTheme/customHeaders/homeHeader.php'); //include this header on home page
    } elseif ( is_single() ) {
    include (TEMPLATEPATH . '/../ARHealthCareersFrameTheme/customHeaders/homeHeader.php'); //include this header on posts
    } elseif ( is_page('Why We're Here') ) {
    include (TEMPLATEPATH . '/../ARHealthCareersFrameTheme/customHeaders/homeHeader.php'); //include this header on about page
    } else {
    include (TEMPLATEPATH . '/../ARHealthCareersFrameTheme/customHeaders/communityHeader.php'); //include this header on BuddyPress pages
    } ?>

    Still, it seems like I should just be able to use the BP conditionals to find out which specific BP page I’m on and display content accordingly.

    #55215
    Jeff Sayre
    Participant

    I’m afraid if the developer of that plugin is not responding to your questions, then that may very well indicate that they have stopped supporting the plugin. You should post (if you have not already) on the WPMU forums and see if anyone has information.

    Perhaps someone there may know of an alternative or will adopt the plugin and bring it up to code. Make sure you mention that you want to use this plugin in BuddyPress.

    #55214
    Jeff Sayre
    Participant

    @pxlgirl

    If my component is deemed worthy enough to be integrated in some form or fashion into core, then I imagine what will happen is that it will show up in a bleeding-edge trunk version.

    If not, then I will gladly release it as a plugin until another solution becomes available in Core.

    #55207
    Paul Wong-Gibbs
    Keymaster

    For Ousep’s post:

    Do I really have to use the bp-sn-whatever template to be able to use any of buddypress's functionality?

    No. Just like WordPress has its famouse “Loop”, BuddyPress implements its own Loops for all of the core components and features. See https://codex.buddypress.org/developer-docs/custom-buddypress-loops/.

    There is a range of different theme information on the Codex, but you are able to copy all of the templates from the BuddyPress parent theme into any WordPress theme and it will work. You will need to add custom CSS to style those elements, obviously.

    #55206
    Paul Wong-Gibbs
    Keymaster

    DJPAUL IS CRIT BY A WALL OF TEXT FOR 100,000,000 DAMAGE AND DIES.

    https://codex.buddypress.org/developer-docs/action-reference/ lists the actions for the controller code for BuddyPress. A one-minute search of the codex doesn’t show a page of the actions in the theme. If you think this will be useful you are able to add/edit pages on the BuddyPress Codex.

    #55205

    In reply to: Error on install

    Paul Wong-Gibbs
    Keymaster
    #55204
    outolumo
    Participant

    I just went through the default bp-sn-parent theme and harvested all the action hooks beginning with bp_ to a list. Could someone put it to the codex? This list could be useful for people developing their own BuddyPress themes. I hope I didn’t miss anything.

    Because these hooks appear in the default BuddyPress theme, some plugin developers might assume their existance in bp-themes. Therefore they should probably exist somewhere in the custom template files. Most of these are are fairly generic and could be filtered into existing themes (e.g. bp_head() could be filtered using wp_head() hook), assuming that the theme you are building on is properly saturated with hooks.

    Note that the optionsbar.php, userbar.php and plugin-template.php need to be added to your theme. I don’t know if they could be filtered.

    The notable exception being the search-login-bar and nav-items. IMO they shouldn’t be in the BuddyPress template at all. Better solution would be to have functions for search-box & login widget, and insert them to the template using tags for those. This would make them both more reusable – e.g. search-box could be re-used on search and 404 templates – and flexible, allowing to login box to appear separate from the search box. Likewise the nav-menu should be widgetized, i.e. made a function that can be called somewhere from the page.

    While not exactly a template tag issue, theme developers should be aware that the buddypress admin bar is by default activated at the wp_footer() as follows:

    add_action( ‘wp_footer’, ‘bp_core_admin_bar’, 8 );

    I’m gonna try placing the following to the functions.php:

    remove_action(‘wp_footer’, ‘bp_core_admin_bar’, 8);

    add_action( ‘i_want_it_here_tag’, ‘bp_core_admin_bar’, 8 );

    ====================================================

    header.php

    <?php do_action( ‘bp_head’ ) ?> (In the head section.)

    <?php do_action( ‘bp_before_search_login_bar’ ) ?>

    <?php do_action( ‘bp_login_bar_logged_out’ ) ?>

    <?php do_action( ‘bp_login_bar_logged_in’ ) ?>

    <?php do_action( ‘bp_search_login_bar’ ) ?>

    <?php do_action( ‘bp_after_search_login_bar’ ) ?>

    <?php do_action( ‘bp_before_header’ ) ?>

    <?php do_action( ‘bp_nav_items’ ); ?>

    <?php do_action( ‘bp_header’ ) ?>

    <?php do_action( ‘bp_after_header’ ) ?>

    <?php do_action( ‘bp_before_container’ ) ?>

    ====================================================

    footer.php

    <?php do_action( ‘bp_after_container’ ) ?>

    <?php do_action( ‘bp_before_footer’ ) ?>

    <?php do_action( ‘bp_footer’ ) ?>

    <?php do_action( ‘bp_after_footer’ ) ?>

    ====================================================

    Content wrappers: inside #container, but containing #content.

    index.php

    <?php do_action( ‘bp_before_blog_home’ ) ?>

    <?php do_action( ‘bp_after_blog_home’ ) ?>

    single.php

    <?php do_action( ‘bp_before_blog_single_post’ ) ?>

    <?php do_action( ‘bp_after_blog_single_post’ ) ?>

    404.php

    <?php do_action( ‘bp_before_404’ ) ?>

    <?php do_action( ‘bp_after_404’ ) ?>

    archive.php

    <?php do_action( ‘bp_before_archive’ ) ?>

    <?php do_action( ‘bp_after_archive’ ) ?>

    page.php

    <?php do_action( ‘bp_before_blog_page’ ) ?>

    <?php do_action( ‘bp_after_blog_page’ ) ?>

    attachment.php

    <?php do_action( ‘bp_before_attachment’ ) ?><

    <?php do_action( ‘bp_after_attachment’ ) ?>

    links.php

    <?php do_action( ‘bp_before_blog_links’ ) ?>

    <?php do_action( ‘bp_after_blog_links’ ) ?>

    search.php

    <?php do_action( ‘bp_before_blog_search’ ) ?>

    <?php do_action( ‘bp_after_blog_search’ ) ?>

    ====================================================

    Post wrappers – everything within the Loop. N.B. not every loop is listed here.

    index.php, single.php, archive.php, attachment.pgp, search.php

    <?php do_action( ‘bp_before_blog_post’ ) ?>

    <?php do_action( ‘bp_after_blog_post’ ) ?>

    ====================================================

    Some specific tags allowing to replace the entire loop:

    404.php

    <?php do_action( ‘bp_404’ ) ?>

    search.php

    <?php do_action( ‘bp_blog_post’ ) ?>

    ====================================================

    The mandatory Buddypress templates:

    optionsbar.php

    <?php do_action( ‘bp_before_options_bar’ ) ?>

    <?php do_action( ‘bp_inside_before_options_bar’ ) ?>

    <?php do_action( ‘bp_inside_after_options_bar’ ) ?>

    <?php do_action( ‘bp_after_options_bar’ ) ?>

    userbar.php

    <?php do_action( ‘bp_before_user_bar’ ) ?>

    <?php do_action( ‘bp_inside_before_user_bar’ ) ?>

    <?php do_action( ‘bp_inside_after_user_bar’ ) ?>

    <?php do_action( ‘bp_after_user_bar’ ) ?>

    plugin-template.php

    <?php do_action(‘bp_template_content_header’) ?>

    <?php do_action(‘bp_template_title’) ?>

    <?php do_action(‘bp_template_content’) ?>

    =================================

    Special templates:

    comments.php

    <?php do_action( ‘bp_before_blog_comment_list’ ) ?>

    <?php do_action( ‘bp_after_blog_comment_list’ ) ?>

    <?php do_action( ‘bp_before_blog_comment_form’ ) ?>

    <?php do_action( ‘bp_blog_comment_form’ ) ?>

    <?php do_action( ‘bp_after_blog_comment_form’ ) ?>

    searchform.php

    <?php do_action( ‘bp_before_blog_search_form’ ) ?>

    <?php do_action( ‘bp_blog_search_form’ ) ?>

    <?php do_action( ‘bp_after_blog_search_form’ ) ?>

    sidebar.php

    <?php do_action( ‘bp_before_blog_sidebar’ ) ?>

    <?php do_action( ‘bp_inside_before_blog_sidebar’ ) ?>

    <?php do_action( ‘bp_inside_after_blog_sidebar’ ) ?>

    <?php do_action( ‘bp_after_blog_sidebar’ ) ?>

    More details about how these tags are applied can be found by looking at the files in the bp-sn-parent -theme.

    #55189
    slicktig1
    Participant

    thanks for the reply . Is there a way we could tune the buddypress themes for members? If buddypress cannot be used on member blogs how would members ever visit social links like blogs,members,forums etc., ?

    #55183
    pxlgirl
    Participant

    Jeff, are you going to release it as an external plugin before it will be taken to core or not? Keep up the great work btw! :D

    pxlgirl.

    #55180

    In reply to: New forums

    Technically, yes. To take advantage of BuddyPress forums for 1.1.1 and how they work “out of the box” that’s what it needs. It shouldn’t take more than an hour or so to create groups and map their forum_id’s to your old forums in phpMyAdmin.

    When you upgrade, be sure to choose the “existing forum” method so that BuddyPress knows to use your existing tables and doesn’t create new ones.

    #55176

    Check buddypress/bp-activity/bp-activity-filters.php for a list of what it’s being run through already.

    bp_get_activity_content

    …is the name of the filter you will want to use, just like BuddyPress already does.

    You could make your own custom kses for it, or if you’d rather try strip_tags give something like this a shot?

    http://pastebin.com/m9cb9d10

    The problem with that code (as it is) is that the activity stream contains the href’s and spans for the links to users and the time, so I don’t think strip_tags will really work. You’ll probably have to put your own kses in there honestly.

    #55175

    Using BuddyPress will ensure constant, future-proof development. I think using it instead of a random authors plugin is probably the best thing to do.

    You’re still going to need to adapt to WordPress being a slave to BuddyPress for all of the ways that BP hooks into and filters things like themes.

    BP assumes that you’re going to use most of its components, and if you turn them off it’s kind of up to you as the site author/admin to adjust accordingly.

    #55174

    In reply to: Fixed the 404 Problem!

    This is only the case if you’re using a custom theme and you’re not making it a child of the bp-sn-parent theme. Check the links below for more info…

    https://codex.buddypress.org/how-to-guides/upgrading-a-buddypress-1-0-theme-for-buddypress-1-1/

    https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/

    #55173

    The privacy component is so good, that it’s set to “private” in the core and you can’t even find it! ;)

    At the moment you would need to code your own registration functions to work in place of the BuddyPress ones to do this. Basically a copy and paste job and rearrange the registration steps to work how you want them to, then call the custom functions in your template instead of the BuddyPress ones.

    #55168
    Zohar Babin
    Participant

    Guys,

    Finally it’s here. with the great contribution of rtCamp*, you can now download the Kaltura-BuddyPress component:

    http://www.kaltura.org/project/buddypress-kaltura

    Please share your thoughts and feedback on the kaltura.org forums.

    #55163
    Jeff Sayre
    Participant

    As you said in you OP, modifying the core file is a BIG mistake. Instead, place all your custom code in a file called bp-custom.php. Then place that file in /wp-contents/plugins/.

    #55162
    Jeff Sayre
    Participant

    You are talking about building your own custom theme. Two pieces of advice. Read the BuddyPress Codex articles on theming found here:

    And secondly, use Firefox with FireBug.

    #55157
    Jeff Sayre
    Participant

    Dido exactly what Paul just said above!

    Since Privacy is slated to be a Core BP component, I decided that my plugin needs to be first vetted through Andy before releasing it to the general community. I do not want people to simply assume that my work is the official version.

    When it is decided whether or not my plugin will in some form or fashion become the Core privacy component, then I will post back here and let everyone know.

    #55156
    Jeff Sayre
    Participant

    Also, a kind reminder about the Domain Policy.

    #55153
    Paul Wong-Gibbs
    Keymaster

    Jeff’s component is still under some stage of review and AFAIK hasn’t been released for private testing yet. There’s no promise that Jeff’s code will get integrated into the BP Core, that decision is Andy Peatling’s.

    I’d assume the plan is to get a plugin out that is compatible with BP 1.1 as BP 1.2 isn’t likely to be released until January.

    #55148
    bpisimone
    Participant

    What 21cdb described (Travel Junkie’s method) works. Not in the functions.php but at least in bp-custom.

    #55147
    madloki
    Participant

    Fantastic :) Is there an official release for bp 1.2 with your pc plugin jeff?

    #55145
    floboy
    Participant

    wolfapache9516, I will like to know how you resolve this. I see that your buddypress theme is fine now.

Viewing 25 results - 61,451 through 61,475 (of 69,046 total)
Skip to toolbar