Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'Add BuddyPress Styles to a Theme'

Viewing 25 results - 276 through 300 (of 381 total)
  • Author
    Search Results
  • @mercime
    Participant

    @kkradel bp.css is enqueued after your style.css and bp.css has this in stylesheet
    `#wp-admin-bar .padder {
    width: 95% !important; /* Line up the admin bar with the content body in this theme */
    }`

    The easiest thing to do is to
    1 – download a copy of bp.css https://plugins.svn.wordpress.org/bp-template-pack/tags/1.2/bp.css
    2 – correct the width of #wp-admin-bar .padder to 100%
    3 – upload to server in plugins/bp-template-pack to override old bp.css

    @r-a-y, can i just add the following code to my child theme function.php and define my custom css in style.css as i dont want to use default theme css.

    `if ( !function_exists( ‘bp_dtheme_enqueue_styles’ ) ) :
    function bp_dtheme_enqueue_styles() {}
    endif;`

    i will like to use my custom css.
    Regards

    #120340
    Tammie Lister
    Moderator

    @valuser: Are you enqueuing your CSS for the custom styles you’ve done. To me it looks like you aren’t. There are 2 things at play here:

    1. You need to now enqueue any styles keeping order ie; last style you want enqueue that last

    2. !important is a little like a kid sticking their hand up in class it will get paid attention to above all else – therefore yes adding !important does work but shouldn’t be what you use you should use the ‘cascading’ nature of CSS.

    Quint
    Participant

    @boonebgorges, okay Boone, I’ve spent the last 6 hrs 16 minutes on this. I have determined where the issue is occurring but I do not know how to fix it. But first here’s the calibration I eventually got to: I re-installed WordPress and Buddypress (yep, I’m getting faster reinstalling this stuff). ;-) I created a new child theme; that is, a new style.css file and a new functions.php file to enqueue the child’s style.css file. Here’s the code for my functions.php file:

    `<?php

    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 );

    wp_enqueue_style( ‘bp-child-style’, get_stylesheet_directory_uri() . ‘/style.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_print_styles’, ‘bp_dtheme_enqueue_styles’ );

    ?>`

    Should be no issue there. With the new stylesheet I started adding back my old code starting at the very top. I didn’t have to go very far at all. It failed at the body selector (at the very bottom of this post); specifically, the @font-face font that the stylesheet loaded. I took it out; I replaced it with verdana or helvetica. No issues. I cycled through all of the @font-face fonts and each one produced the error. Note: The @font-face fonts rendered properly on every page but failed when I clicked on a “dropdown-style” field as described in my first post. Do you have any recommendations? Am I supposed to enqueue the fonts just as I had the stylesheet? If so, how would that be done? Thanks!

    Note: I commented out a few declarations in the body selector to help narrow down which declaration could be the issue. And just like Firefox, this works fine in Chrome 13.0.782.220.

    `/*
    Theme Name: My BP Default Child Theme 1
    Theme URI: http://folio.com
    Description: This is my first Buddypress Default Child Theme
    Author: Quint A. Rahaman, Jr.
    Template: bp-default
    Tags: buddypress, two-column, grey, dark
    */

    /* RESET – http://meyerweb.com/eric/tools/css/reset/ | v1.0 | 20080212 */
    /*


    */

    body,html{height:100%;}
    html,body,div,span,applet,object,iframe,h1,h2,h3,h4,h5,h6,p,blockquote,pre,a,acronym,address,big,cite,code,del,dfn,em,font,img,ins,kbd,q,s,samp,small,strike,strong,sub,sup,tt,var,b,u,i,center,dl,dt,dd,ol,ul,li,fieldset,form,label,legend,table,caption,tbody,tfoot,thead,tr,th,td{border:0;outline:0;font-size:100%;vertical-align:top;background:transparent;margin:0;padding:0;}
    body{line-height:1;}
    ol,ul{list-style:none;}
    blockquote,q{quotes:none;}
    blockquote:before,blockquote:after,q:before,q:after{content:none;}
    :focus{outline:0;}
    del{text-decoration:line-through;}
    table{border-collapse:collapse;border-spacing:0;}

    /* Floating & Alignment */
    .fl{float:left;}
    .fr{float:right;}
    .ac{text-align:center;}
    .ar{text-align:right;}

    /* Clear Floats */
    .col-full:after{content:”.”;display:block;height:0;clear:both;visibility:hidden;}
    .fix{clear:both;height:1px;overflow:hidden;margin:-1px 0 0;}
    html body * span.clear,html body * div.clear,html body * li.clear,html body * dd.clear{background:none;border:0;clear:both;display:block;float:none;font-size:0;list-style:none;overflow:hidden;visibility:hidden;width:0;height:0;margin:0;padding:0;}

    /* Generated by Font Squirrel (http://www.fontsquirrel.com) on September 8, 2011 */

    @font-face {
    font-family: ‘FontSiteSansRoman’;
    src: url(‘includes/fonts/includes/fonts/fontsitesans-roman-webfont.eot’);
    src: url(‘includes/fonts/fontsitesans-roman-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/fontsitesans-roman-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/fontsitesans-roman-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/fontsitesans-roman-webfont.svg#FontSiteSansRoman’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘BergamoStdItalic’;
    src: url(‘includes/fonts/bergamostd-italic-webfont.eot’);
    src: url(‘includes/fonts/bergamostd-italic-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/bergamostd-italic-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/bergamostd-italic-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/bergamostd-italic-webfont.svg#BergamoStdItalic’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘BergamoStdRegular’;
    src: url(‘includes/fonts/bergamostd-regular-webfont.eot’);
    src: url(‘includes/fonts/bergamostd-regular-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/bergamostd-regular-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/bergamostd-regular-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/bergamostd-regular-webfont.svg#BergamoStdRegular’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘FontSiteSansCondensed’;
    src: url(‘includes/fonts/fontsitesans-cond-webfont.eot’);
    src: url(‘includes/fonts/fontsitesans-cond-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/fontsitesans-cond-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/fontsitesans-cond-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/fontsitesans-cond-webfont.svg#FontSiteSansCondensed’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘FontSiteSansUltraLight’;
    src: url(‘includes/fonts/fontsitesans-ultralight-webfont.eot’);
    src: url(‘includes/fonts/fontsitesans-ultralight-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/fontsitesans-ultralight-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/fontsitesans-ultralight-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/fontsitesans-ultralight-webfont.svg#FontSiteSansUltraLight’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘StMarieThin’;
    src: url(‘includes/fonts/stmarie-thin-webfont.eot’);
    src: url(‘includes/fonts/stmarie-thin-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/stmarie-thin-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/stmarie-thin-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/stmarie-thin-webfont.svg#StMarieThin’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘BergamoStdItalic’;
    src: url(‘includes/fonts/bergamostd-italic-webfont.eot’);
    src: url(‘includes/fonts/bergamostd-italic-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/bergamostd-italic-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/bergamostd-italic-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/bergamostd-italic-webfont.svg#BergamoStdItalic’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘BergamoStdItalic’;
    src: url(‘includes/fonts/bergamostd-italic-webfont.eot’);
    src: url(‘includes/fonts/bergamostd-italic-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/bergamostd-italic-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/bergamostd-italic-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/bergamostd-italic-webfont.svg#BergamoStdItalic’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘BergamoStdRegular’;
    src: url(‘includes/fonts/bergamostd-regular-webfont.eot’);
    src: url(‘includes/fonts/bergamostd-regular-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/bergamostd-regular-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/bergamostd-regular-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/bergamostd-regular-webfont.svg#BergamoStdRegular’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘BergamoStdRegular’;
    src: url(‘includes/fonts/bergamostd-regular-webfont.eot’);
    src: url(‘includes/fonts/bergamostd-regular-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/bergamostd-regular-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/bergamostd-regular-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/bergamostd-regular-webfont.svg#BergamoStdRegular’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘FontSiteSansCondensed’;
    src: url(‘includes/fonts/fontsitesans-cond-webfont.eot’);
    src: url(‘includes/fonts/fontsitesans-cond-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/fontsitesans-cond-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/fontsitesans-cond-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/fontsitesans-cond-webfont.svg#FontSiteSansCondensed’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘FontSiteSansCondensed’;
    src: url(‘includes/fonts/fontsitesans-cond-webfont.eot’);
    src: url(‘includes/fonts/fontsitesans-cond-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/fontsitesans-cond-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/fontsitesans-cond-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/fontsitesans-cond-webfont.svg#FontSiteSansCondensed’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘FontSiteSansRoman’;
    src: url(‘includes/fonts/fontsitesans-roman-webfont.eot’);
    src: url(‘includes/fonts/fontsitesans-roman-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/fontsitesans-roman-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/fontsitesans-roman-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/fontsitesans-roman-webfont.svg#FontSiteSansRoman’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘FontSiteSansRoman’;
    src: url(‘includes/fonts/fontsitesans-roman-webfont.eot’);
    src: url(‘includes/fonts/fontsitesans-roman-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/fontsitesans-roman-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/fontsitesans-roman-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/fontsitesans-roman-webfont.svg#FontSiteSansRoman’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘FontSiteSansUltraLight’;
    src: url(‘includes/fonts/fontsitesans-ultralight-webfont.eot’);
    src: url(‘includes/fonts/fontsitesans-ultralight-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/fontsitesans-ultralight-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/fontsitesans-ultralight-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/fontsitesans-ultralight-webfont.svg#FontSiteSansUltraLight’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘FontSiteSansUltraLight’;
    src: url(‘includes/fonts/fontsitesans-ultralight-webfont.eot’);
    src: url(‘includes/fonts/fontsitesans-ultralight-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/fontsitesans-ultralight-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/fontsitesans-ultralight-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/fontsitesans-ultralight-webfont.svg#FontSiteSansUltraLight’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘StMarieThin’;
    src: url(‘includes/fonts/stmarie-thin-webfont.eot’);
    src: url(‘includes/fonts/stmarie-thin-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/stmarie-thin-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/stmarie-thin-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/stmarie-thin-webfont.svg#StMarieThin’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    @font-face {
    font-family: ‘StMarieThin’;
    src: url(‘includes/fonts/stmarie-thin-webfont.eot’);
    src: url(‘includes/fonts/stmarie-thin-webfont.eot?#iefix’) format(’embedded-opentype’),
    url(‘includes/fonts/stmarie-thin-webfont.woff’) format(‘woff’),
    url(‘includes/fonts/stmarie-thin-webfont.ttf’) format(‘truetype’),
    url(‘includes/fonts/stmarie-thin-webfont.svg#StMarieThin’) format(‘svg’);
    font-weight: normal;
    font-style: normal;

    }

    #sidebar{display:none;}
    div#content .padder{margin-right:0px; border-right-width:0px;}

    body { font-family: ‘FontSiteSansRoman’, helvetica, sans-serif;
    /* font-size: 0.75em;
    line-height: 1.5em;*/
    color: #3e3e3e;
    background: url(“images/bg.png”) repeat fixed 0 0 #f6f0d6;
    /* max-width: none;
    width: 100%;*/
    /* position: relative;*/
    }`

    #119577
    @mercime
    Participant

    Make sure that you added term buddypress to tags in your child theme’s stylesheet
    `Tags: buddypress, etc. etc. etc.`

    Another way would be to add the following line to your wp-config.php
    `define( ‘BP_SILENCE_THEME_NOTICE’, true );`

    The first one is easier I think :-)

    Quint
    Participant

    @gregfielding: Could you let me know what step I’m missing or applying incorrectly? I have the same issue that you mentioned in your original post. So, after reading all of the recommended material regarding creating a child theme for BP 1.5 Beta 1 thru 3, the styling in my child’s style.css file still won’t be recognized (And I’m still in a slowly clearing fog. Too slow.). Here’s what I did:

    1. Created my child theme folder,
    2. In that I created a blank functions.php file and then added to it:

    `<?php
    if ( !function_exists( ‘bp_dtheme_enqueue_styles’ ) ) :
    function bp_dtheme_enqueue_styles() {}
    endif;
    ?>`

    3. I reloaded my browser, and the default styling isn’t there. Great.
    4. Now, to my child’s style.css file, I do what I’ve done before and add the @import code:
    @import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/default.css );
    5. I did Step 4 because I want to load and override the default styling, not start from scratch.

    Could you point me in the right direction? Thanks.

    @mercime
    Participant

    @gregfielding I know what you mean :-)

    As DJPaul mentioned here, child themes can declare and empty function to override parent theme’s function. Check out Boone’s solution – a proposed patch which works of course and is better IMHO.

    You might have noticed that the link to stylesheet is no longer in bp-default theme’s header.php. Hence, you could either add the link to stylesheet in child theme’s header.php or enqueue main stylesheet ala bp-default theme.

    Cheers.

    #118552

    In reply to: Frisco Child Theme

    David Carson
    Participant

    Thanks for your help testing it out and reporting issues, @InterMike.

    I’ve just added a theme options page so that users can choose from a few basic color choices and use a custom.css stylesheet if they want to override anything. Aiming to get some other basic options in there for fonts.

    For the custom stylesheet, check off the custom stylesheet option box in theme options, and create custom.css in the root theme directory.

    A reminder that Frisco requires BuddyPress 1.5 and WordPress 3.2.1 or 3.3 (nightly build).

    You can download the theme at https://github.com/davidtcarson/frisco/

    #116169
    astromono
    Participant

    @mercime Well, I’m using a child theme based off on bp-default, which is the default BP theme. Thing is, now I recall doing this in my new stylesheet when I first created the child theme:

    /* Inherit the default theme adminbar styles */

    @import
    url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );

    I tried importing the styles for the default theme and the adminbar.css within the same style.css for my child theme. Could that be the issue?

    I just tried adding the above changes and the issue isn’t resolved.

    ARHistoryHub
    Participant

    Assuming you’re already loading jQuery in your header with something like this ` ` just add the following before the “ tag…
    `
    jQuery(document).ready(function(){

    jQuery(‘#object-nav a, #subnav a’).live(‘click’, function(e){
    e.preventDefault();
    var link = jQuery(this).attr(‘href’);
    jQuery(‘#nav-ajax’).html(‘

    Loading

    ‘);
    jQuery(‘#nav-ajax’).load(link+’ #nav-ajax’);

    });

    });
    `
    To write this script, I chose what links I wanted to make the call – for profile navigation that’s those in #object-nav and #subnav.
    Then you have to wrap the elements you want to get loaded in a div – in this case I used `

    ` and wrapped it around the entire item-body div in my theme’s members/single/home.php…. Like so
    `



    `

    You also have to do the same thing for the members/single/plugins.php with the same div. Just style the p class=”ajaxing” however you want in your default stylesheet. The process works the same for groups as well. I had problems getting a:active css attributes to show, but besides that it’s worked just fine.

    Oh, and thanks for the compliments!

    #115158
    Marian
    Participant

    @en0ch

    So sorry I didn’t see your request for more help. I have my settings to be notified of any @mentions and replies to my forum posts but for some reason I did not receive any notification that you had replied. Not sure if it’s a problem with BuddyPress.org notifications or what.

    Anyway, it’s probably too late and you hopefully found a solution already, but I’ll post this here just in case you or anyone else are still looking for a way to disable the random visit menu in the BuddyPress admin bar without disabling the admin bar itself.

    Rather than explain the inadequate solution of changing #bp-adminbar-visitrandom-menu display to none in the stylesheet, let me give the function override solution instead:

    In your theme’s footer.php file, right BEFORE it says “, add the following code:
    `
    <?php
    if (!is_user_logged_in()) {
    remove_action( ‘bp_adminbar_menus’, ‘bp_adminbar_random_menu’, 100 );
    }
    ?>
    `
    That’s if you want the random visit menu to be removed only for users who are not logged in.

    If you want it to be removed for all users, whether or not they’re logged in, use this simpler code instead:
    `
    <?php
    remove_action( ‘bp_adminbar_menus’, ‘bp_adminbar_random_menu’, 100 );
    ?>
    `

    I see that the font for the code I just posted is not clearly legible in places. Please note that the remove_action line ends with a semi-colon ;

    HTH
    :-)
    Marian

    #115107
    Virtuali
    Member

    Do you have template pack installed? If you do, all the files you need to edit are currently in your theme folder via FTP.

    For example, yourtheme/members/single

    To edit styles, template pack, or buddypress doesn’t add any styles to buddypress by default. You can add them by adding this to your current CSS.

    `/* Inherit the default theme styles */
    @import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/default.css );

    /* Inherit the default theme adminbar styles */
    @import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );`

    Then, of coarse, edit the CSS to what you like.

    #115069
    @mercime
    Participant

    @hnla this worked for me in child theme
    `add_action( ‘wp_print_styles’, ‘our_deregister_bp_dtheme_styles’, 100 );
    function our_deregister_bp_dtheme_styles() {
    wp_deregister_style( ‘bp-default-reset’ );
    wp_deregister_style( ‘bp-default-main’ );
    }`

    #114830
    @mercime
    Participant

    It’s because the number of words/characters in the excerpts are not the same. Since you’re using a child theme of premium Genesis theme, I suggest that you get the free support included in your purchase of the theme/child theme and inquire about how to increase/decrease number of words/characters in the featured excerpts. While you’re there, might as well get find limits for the title for featured articles as well since there could be times where your post title would be longer than one line.

    An alternative would be as simple as making changes to your stylesheet to set the height of the featured article containers so assuming you’ve got the same number of articles on the left as well as on the right, all will be leveled to same height. In your case, add something like this to your child theme’s stylesheet:

    `#content .featuredpost .post {
    height: 150px;
    position: relative;
    }`

    `#content .featuredpost .post a.more-link {
    position: absolute;
    bottom: 5px;
    right: 5px;
    }`

    Adjust height of `#content .featuredpost .post` to taste.

    EDIT – @hnla, here I go again, took too much time to answer the question :-)

    #114779
    d71
    Member

    Ok, so in the working default BuddyPress theme the Ajax handler works great:

    bp_dtheme_post_update traceback:

    #0 bp_dtheme_post_update() called at [:]

    #1 call_user_func_array() called at
    [wp-includes/plugin.php:395]

    #2 do_action() called at
    [wp-content/plugins/buddypress/bp-core.php:2026]

    #3 bp_core_add_ajax_hook() called at [:]

    #4 call_user_func_array() called at
    [wp-includes/plugin.php:395]

    #5 do_action() called at
    [wp-settings.php:298]

    #6 require_once(/home2/capacoac/public_html/artsbeta/wp-settings.php) called at
    [wp-config.php:91]

    #7 require_once(/home2/capacoac/public_html/artsbeta/wp-config.php) called at
    [wp-load.php:30]

    When doing a normal status update it seems to flow normally:

    top of bp_dtheme_post_update in bp-theme-default…
    . content=james
    . object=
    . calling bp_activity_post_update (no object)…
    . calling user func tag=wp_default_styles

    My status update was “james”. So all working well for the default BuddyPress theme.

    Now with BuddyBase activated none of that entire call chain happens and neither does it happen from the default buddy base theme. its like ajax.php is no longer being loaded.

    To verify I put an error_log call at the top of the BuddyBase copy of _inc/ajax.php, just to indicate that _its_ version of ajax.php was being loaded…and its not. For some reason the BuddyBase theme is not having its version of ajax.php loaded.

    I’m not really sure hwo to verify how the theme tells WordPress/BuddyPress to load that file, but I guess I have another lead to track down….

    #114730
    sidjags
    Member

    @DoctorDR looks like i’ve found the solution… and i hope everyone out there will find this helpful too.
    Problem Statement: I wanted to have a custom set of 10-15 avatars uploaded into a folder, and buddypress would have to pick from any one of these to assign to members(on random) everytime then login if they havent uploaded their pwn profile pic.
    Why: Lets say am on the members page, and everyone is displayed over there.. we can get different custom pics rather than just one custom pic.
    Solution:
    Step#1: Change the settings to “mystery man” in your buddypress backend.
    Step#2: Upload pics into a folder in your child theme (i uploaded them into wp-content/themes/default/images/avatars/ ).. my theme name is : default, and in it i made a folder for images, and once again another folder called avatars. now… within avatars i put in 10 pics named the following “1avatar.png”, “2avatar.png”, “3avatar.png”… and so on… till “9avatar.png”
    and lastly…
    Step #3: Paste the following code in your functions.php child theme (taken from a combination of other sources)

    `function myavatar_add_default_avatar( $url )
    {
    $length=1;
    $characters=’123456789′;
    $string=”;
    for ($p = 0; $p < $length; $p++) {
    $string .= $characters[mt_rand(0, strlen($characters))];
    }

    return get_stylesheet_directory_uri() .’/images/avatars/’.$string.’avatar.png’;
    }
    add_filter( ‘bp_core_mysteryman_src’, ‘myavatar_add_default_avatar’ );`

    and thats it… give it a shot… worked great for me! i hope this helps others too cause i saw a lot of people asking for this to no avail…

    sidjags
    Member

    @hal9000 to get alternating colors on any of your loops (activity, members, groups, blog listings, forums, whatever)… using this code (uses CSS3)

    li { background: green; }
    li:nth-child(odd) { background: red; }

    more specifically:
    in the default.css stylesheet of the buddypress default theme… you should find on line 396:
    ul.item-list li {
    position: relative;
    padding: 15px 0;
    border-bottom: 1px solid #eaeaea;
    }

    replace that with this:
    ul.item-list li {
    position: relative;
    padding: 15px 0;
    border-bottom: none;
    background: green;
    }

    ul.item-list li:nth-child(odd) {
    background: red;
    }

    and wolla!! ofcourse… please change the red and green to the colors of your theme… also, if you need it specifically for members, or groups, etc… then in the source code of each page , for eg, in groups, it is under a particular id: groups-list… put the styles under that id and so on.. hope that makes sense to you.

    #113645
    Hugo Ashmore
    Participant

    @4ella no DO use a child theme, if all you want to do is some basic CSS styling ten you only nee to create the most basic child theme with a style.css file in it.

    Follow this guide it’s very straightforward:
    https://codex.buddypress.org/theme-development/building-a-buddypress-child-theme/

    If you now activate your theme in the dashboard it will inherit/ import the main BP styles as well as all the other important BP stuff, you can now add your own styles to your stylesheet below the @ import calls to override any BP styles.

    #113530

    In reply to: Centering a Photo

    pcwriter
    Participant

    @BrainiacWebDesigns

    Do you still have a plugin activated that modifies wp-login.php? If so, deactivate it.
    Also check your theme’s main stylesheet to see if any styles are applied to div#login h1 a ‘cuz Firebug shows margins left & right:-90px

    If you can’t find anything, try adding the following to your theme’s stylesheet to override whatever’s causing those weird margins:
    div#login h1 a {margin:0; !important}

    #112813
    @mercime
    Participant

    In the meantime, as of BP 1.3 trunk-4414

    1. open up https://buddypress.trac.wordpress.org/browser/trunk/bp-themes/bp-default/functions.php

    2. comment out line # 163 and lines #170 to #175

    3. add to your child theme’s stylesheet
    `@ import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/reset.css );
    @ import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/default.css );
    @ import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );`
    delete space between `@` and `import`

    #112571
    @mercime
    Participant

    @1stAngel I have not used the Atahualpa theme but try adding this to your theme’s style.css file :

    `/* Inherit the default theme adminbar styles */
    @import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );

    #112238
    acustica
    Member

    I was having this same problem and posted a lengthy comment about it in the trac ticket mentioned above ( https://trac.buddypress.org/ticket/2647 ), but in the meantime, I developed a workaround that works on my site and doesn’t require modifying any core files (and will fix the problem in any BP component, not just with friend request emails).

    Just add the following function (a filter) to your theme’s functions.php file:
    `
    /**
    * Intercept bp_core_catch_no_access() when nothing is set to enable smart login page redirects
    * and prevent BP from just redirecting the user to the homepage
    *
    * @param string $found_template The result of locate_template() call
    * @param mixed $templates Not sure what it’s for, but it’s generally bool false
    */
    function yourtheme_load_template_filter( $found_template, $templates ) {
    if ( ! $templates && empty( $found_template ) ) {
    // just set it as default theme file so that file_exists() returns true
    $found_template = get_stylesheet_directory() . ‘/index.php’;
    }
    return $found_template;
    }
    add_filter( ‘bp_located_template’, ‘yourtheme_load_template_filter’, 11, 2 );
    `

    It’s not a good permanent solution, but I haven’t noticed it affecting anything else (including BP 404s) on my site, and it leaves your BP install happily untouched. If the issue is fixed in the future, of course, I would highly recommend removing this fix, but as far as I can tell, it’s harmless, and certainly makes your site far more usable.

    #109293
    steliodj
    Member

    Hi one more time mercime…i notice something weird, when i’m changing something in css(this happens only to those pages that i have the issue) and inspect with firebug i can see the change is there, but when i use inspect element from chrom or from opera i don’t see the change and it evens grabs css styling information from another line of the stylesheet.

    For example this is what i get(this correct) in firefox when inspecting a specific element:

    `
    div#content form#members-directory-form.dir-form div.item-list-tabs {
    background: url(“../../themes/theme/images/members_directory_menu_bg.png”) no-repeat scroll left top transparent;
    border: medium none;
    clear: both;
    overflow: hidden;
    padding-bottom: 17px;
    padding-top: 15px;
    width: 102%;
    }
    `
    And this is what what i get when inspecting the same element in chrome:

    `
    div.item-list-tabs {
    border: none;
    overflow: hidden;
    clear: both;
    background: url(../../themes/theme/images/buddypress_nav_bg.png) top left no-repeat;
    padding-top: 15px;
    width: 102%;
    padding-bottom: 17px;
    }
    `

    if i remove `form#members-directory-form.dir-form` and keep only `div#content div.item-list-tabs` from my style it works also in chrome but it breaks something else that needs to use another background image and has the same id `div.item-list-tabs`

    Please advice

    #108893
    imjscn
    Participant

    @tim , yes , if you don’t need to use original js/css, then, you don’t need to register them back
    `function my_jscss_remover() {
    wp_deregister_script( ‘the-handle-name’ );
    //and others;
    }
    add_action( ‘after_setup_theme’, ‘my_jscss_remover’ );`
    You can find the “the-handle-name” in the plugin’s files at the line when it load the js/css, it normally use wp_enqueue_script , or wp_enqueue_styles, to load js/css. Sometimes they can also use reqire function, but as long as you find the specific file.js , that’s the line.

    When you register your own js, the final parameter “true” means put it in footer. If your js require to run before the page finish loading, you don’t need this “true”.
    You can also add like this: if bp_is_page(‘xyz’), then, the js will be loaded only on the page you need.
    Please remember that, at this point, your js/css are not minified yet.

    #108781
    Boone Gorges
    Keymaster

    Adding bp_adminbar_notifications_menu() in your header will probably work (as long as it’s nested inside of a `

      ` element), but you will need to modify the styles. You can go in one of two directions.

      One, you can try to bring over the styles from bp-default/_inc/css/adminbar.css. You can import that entire stylesheet into your child theme with this line at the top of your child theme’s style.css:
      `@`import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );
      (See https://codex.buddypress.org/theme-development/building-a-buddypress-child-theme/ for more info on BP child themes.) The downside of doing this is that, depending on your theme and the element in which you’re trying to nest the notifications menu, you’re going to have a really hard time getting it to look good with your theme.

      The other method is to skip bp_adminbar_notifications_menu() altogether. Instead, copy the entirety of that function from bp-core/bp-core-adminbar.php into functions.php of you child theme. After you’ve copied it, change the name of the copied function (to something like wwday3_adminbar_notifications_menu() – it doesn’t matter, you just have to avoid duplicate function names). Then – and here’s what will make your life easier – change the markup, and in particular the CSS selectors (classes and ids) being produced by the function, so that it matches the CSS selectors in the existing dropdown menus you’re trying to integrate with. Then, in header.php of your child theme (or wherever you’re currently trying to call bp_adminbar_notifications_menu()), make sure to call this new function instead.

Viewing 25 results - 276 through 300 (of 381 total)
Skip to toolbar