Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'theme'

Viewing 25 results - 27,101 through 27,125 (of 31,072 total)
  • Author
    Search Results
  • #55240
    deuts
    Participant

    Hi Anointed, I was just working around my own bp install. I wanted to display the BP themes within subdomain community. I had community an id of 4. In the buddpress plugin (not the wp-config.php) look for bp-core.php, and change (not add) the “1” in the

    define( 'BP_ROOT_BLOG', 1 );

    to 4. That worked for me so far, I guess. I’m not actually sure if I’m doing exactly the right thing. This thing is not included in the codex, I hope they do document this if this the only tweak you have to make. Likewise, in the forums, it appears there was no definite answer. Hope I helped.

    #55230
    Mark
    Participant

    I tested my site with ie7 and ie8. I could not recreate the issue of the home page left column appearing below the middle and right column on my site (but I did observe this behavior with ie7 on buddypress.org). No other issue mentioned above was observed on my site (except for the one noted below). As I mentioned, I did see this behavior on a public computer/kiosk using IE (given my comments below, it seems more likely that it was ie7).

    You can see (or at least I can) a similar issue regarding the left column loading below the right column when using IE7 at http://buddypress.org (this site). Visit the ‘About’ and ‘Demo’ links (not the actual demo site). There are only 2 columns but the left appears under the right column with ie7.

    The one issue I was able to recreate on my site was the floating submenu when using the WordPress Default 1.6 Blog Theme. No problem with ie8 but with ie7 the buddybar submenus under ‘My Account’ or ‘My Blogs’ float to the right. I logged into http://testbp.org and created a blog with the default theme and found the same behavior when using ie7.

    I don’t think my specific site offers any insight since the issues that can be recreated are evident on buddypress.org and testbp.org (when logged in and using the default blog theme). I find it curious that others aren’t reporting this behavior as it should be easy to replicate.

    #55228
    Jeff Sayre
    Participant

    You’re welcome!

    I’m setting this to resolved. If for some reason you’re still having issues, as the originator of this post, you can always set it back to “not resolved”.

    #55227
    capitalistdog
    Participant

    Thank you both very much for your speedy replies! I am now on the right track, and owe it all to you. :-)

    @Jeff, I have read the readme, but for some reason this simple problem had stumped me.

    Thanks again!

    #55225
    Paul Wong-Gibbs
    Keymaster

    If you haven’t already, copy bp-themes/bp-default and /bp-sn-parent to the normal WordPress theme directory (/wp-content/themes).

    /wp-content/bp-themes/ is for a previous version of BP themes. Unless you know why you might still want to use it, make sure that /wp-content/bp-themes/ does not exist (i.e. delete the folder) else BP will get confused.

    Activate the bp-default theme, put it on your main WPMU blog and it should work.

    EDIT: Jeff won!

    #55224
    Jeff Sayre
    Participant

    The default BP themes are initially located in the /bp-themes/ directory. Although you do not technically have to move them from that location before activating BuddyPress, you will not have access to them until you move the /bp-default/ and /bp-sn-parent/ folders into the /wp-content/themes/ directory.

    Once those two theme folders are moved to the proper place, you then need to log into WPMU as Site Admin and do step 5 under “Installing BuddyPress” here:

    Installation

    Always read the readme.txt files that come with both WPMU and BuddyPress. All the basic information you need to successfully install them and get them working can be found there. More detailed information can be found on the BuddyPress Codex–like the link I provided above.

    #55223
    Jason Giedymin
    Participant

    No stopping you from doing that.

    In the end it ‘is only a theme’.

    The only negative factors (and I have experience with this) is any time there are issues or changes done to the ‘parent’ theme you either have to merge or your done for.

    :-)

    Jason Giedymin
    Participant

    Try these pointers

    – Try and use the intended function in the same manner as the stock theme. To make sure everything works.

    – Understand that forums and topics must exist to be filtered, much like any of the status filters for widgets such as the latest user/group activities.

    – Try using ‘groups_get_by_most_forum_topics()’ function directly in your custom function.

    – Start debugging, turn debugging flags on for your environment, start to modify the source and see whats going on.

    #55220
    fzeidan
    Participant

    I am, I actually copied the entire parent over to the child. Everything works fine except functions.php and the ajax components.

    I don’t mind troubleshooting it myself, but not sure where to start looking. Where in the code does it control which component to load, child or parent?

    I am now thinking of getting rid of the parent all together and just keep a straight theme. I don’t really like this parent child theme. I like the parent as a guiding factor,but not as the controlling theme.

    Any issues with doing so other than updates not taking effect on the now non-existing parent theme?

    #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.

    #55210

    In reply to: Easy Fixed Width Theme

    Bowe
    Participant

    Thank you for this! You rock my friend!

    #55209
    ousep
    Participant

    Well…. it’s that simple?

    i tried it out on a random page, and it worked… but for styling.

    It really should be written somewhere… on the extend/themes page, perhaps. So people put together some themes and populate the page.

    Thanks! You’ve made my life a whole lot easier.

    #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.

    #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.

    #55190
    slicktig1
    Participant

    sorry DJPaul, I just tried with Avenue k9 theme and the issue is same. I believe my issue may not be related to which theme I am using . But some mu configuration. For eg. The urls http://user.musite.com/members , /forums, /groups and /blogs are all giving same error

    “The page you were looking for was not found” . However i can access http://musite.com/members and all other links fine without issue.

    I’m not sure what’s my next step? could you help me.

    #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., ?

    #55184
    Mark
    Participant

    I saw my site on a kiosk with IE8 today. The home page looked as you described. I didn’t know if was a result of IE8 or the resolution of the monitor.

    I also saw that buddybar menus on the bp home page did not appear ‘in front’ of the upper left members, groups, blogs search box and picklist. I didn’t look at all my blog themes but I did notice that WordPress Default 1.6 Theme by Michael Heilemann breaks with BP. The sub menus under “My Blogs”, > Dashboard- New Post- etc, are all disconnected from the menu. They float over to the right. I’ll check it with testbp.org. Is any one else seeing this IE8 buddybar menu behavior on the bp home and default blog theme?

    wpmu 2.8.4, bp 1.1.1

    #55181
    pxlgirl
    Participant

    Hi,

    well, it seems to work here and on the test drive, so it must be my end. I have loaded the default theme as a base and only changed the css settings. I am now using BP 1.1.1.

    Any ideas what might have gone wrong?

    pxlgirl.

    #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/

    #55167
    Paul Wong-Gibbs
    Keymaster

    It looks as if this should be working. Can you clarify if you are creating a child theme from bp-sn-parent?

    #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.

    #55161
    Jeff Sayre
    Participant

    I’m setting this to resolved as the second post indicates that the OP solved their own problem.

    If you are having custom theming issues and are not the OP, then please start a new thread.

    Jeff Sayre
    Participant

    If BP works fine with the default theme and all plugins turned off except BP then it is either a custom theme issue, a conflict with a 3rd-party plugin, or both.

    By the way, this also means temporarily disabling any custom code you may have placed in bp-custom.php. You need to distill your setup down to the lowest common denominator and then add back–one at a time–a new variable (such as the next plugin or a custom theme) until the problem returns.

Viewing 25 results - 27,101 through 27,125 (of 31,072 total)
Skip to toolbar