Skip to:

Forum Replies Created

Viewing 25 replies - 1 through 25 (of 4,358 total)
  • bp_displayed_user_id(); will display the user id on BP screens/loops – but yes user ID’s are WP user ID’s

    The codex though does list basic template tags functions so always check through that first to see if what you need is available.

    @venutius I’ve just updated the repo files, updating the example enqueueing functions as they needed improvement( although I consider that snippet as being a temp provision) and also updated the styles to add min-height and spacing improvements, not sure if that helps your situation but you can further modify those style if needed (just edit the .css version)

    Profile photo of Hugo Ashmore
    Hugo Ashmore


    @venutius Thanks for the write up, hopefully in time the idea may gain traction, as for a handler for loading those snippets I did have one in use locally but code was rough and ready, so may consider re-doing and making available on github, originally the idea was to add a loader for the snippets to the core buddypress-functions.php file where the main stylesheets are loaded from.

    For now all I can suggest I’m afraid is to play around with the min-height properties where they occur as it really is something that can never be a true one size fits all to create boxes unless we start adding JavaScript into the equation to test for the tallest box and set others to that.

    Profile photo of Hugo Ashmore
    Hugo Ashmore


    An aspect like DB is really A WP one rather than BP one. BP as a plugin running under WP uses the DB as created initially by WP so if WP is running or able to run on … then BP will.

    It is recommended that 5.6.0 be used but WP will run on older versions.

    This is the guide you need to read up on:

    Template Hierarchy

    has_directory means that if you click on a BP generated link /groups/type/foo/ or type that as a url/create a link to, then you will see that as the url and the loop will now show only groups of type ‘foo’

    Template hierarchy will allow you to create a file named in this manner:
    index-directory-type-foo.php (file must be a complete one though including WP headers/footers and all parts in-between.)

    This will only be used if looking at those group types in the loop/url but you can now edit that and change as you require and only affect that group type loop directory display.

    I’m afraid the notion of ‘Boxes’ when combined with variable dynamic content never does work (unless one uses javascript trickery, which has it’s own troubles – Masonry) The best one generally can do is id the troublesome elements and give them increased min-height (try locating the property I used to set min-height and increase) or padding to try and force elements to look lined up and outer boxes equal, I’m afraid to a degree it’s a question of playing around maybe limiting data using excerpt functions.

    Really happy to hear the style modules has been of interest though, hope you can adjust the styles to better suit your data.

    What your highlighting are really WP artifacts, Users / user Roles are handled / managed by WP styling the admin would be something outside BP’s control really, BP member loop directory could be styled but currently we don’t add WP user roles as classes to those list items (nor does WP ), also you would want to be careful about exposing certain roles i.e ‘admin’.

    BP core is updated so that member types are now added to the user screens so you’ll be able to style on those and /or you could add member types to match to certain user roles I guess and achieve frontend BP styling that way.

    If you inspect the generated markup you will see that the loop list elements will have a members type class rendered if user has a type you can then use those to effect styling on.

    In the member single screens it’s a little trickier you do have the ability to use the template hierarchy to set a template for a user type (please refer to the codex for instruction) otherwise for the moment you would need to modify the home.php template to add this yourself something like:

    <?php $user_type = bp_get_member_type( bp_displayed_user_id() ); ?>
    <div id="buddypress" class="<?php echo esc_attr( $user_type ); ?>">

    First line is an addition the second you need to modify the existing element to add the class and php – all in a child copy of the home.php template naturally.
    We will update buddpress core to add a class to the body elements for 2.8 as this would be useful and styling could be effected on that too so if you would rather wait for 2.8…

    It sounds like a template issue, there do need to be template revisions, additional template function tags to make this process work as detailed in the codex page here:

    Template Updates 2.7

    Custom themes may well not have updated their templates.

    Registering the new types can be done in theme functions files but then are locked to that theme or site.

    I can confirm point 3 as well and have opened a ticket to look into issues.

    As for point 1 we are looking into this, likely point 3 is part of the same issue.

    This is an announcement thread, please post any issues found to the “How to & Troubleshooting” forum.

    @jj9617 I have split your topic from the announcement thread so it gets better attention from the community.

    Why does this error on the second use of dbDelta() and not the first?

    It might help if WP could be re-installed as a clean copy not as one installed on the back of a server script installer, which can sometimes cause issues.

    You’ll probably need to be a little more specific as to what you have done and are looking to control. BP provides many paths to custom styling you can create a child theme and then copy various BP templates or the stylesheets to it to modify, or you can create a new buddypress.php template from the themes page.php and redefine the get_template calls for header or footer so new unique ones are called when BP screens are being shown.

    The BP codex has all these details, have a hunt through the theme section and a read of the template hierarchy to learn how you can introduce new template parts.

    But re-state what you’re trying to do in a little more detail as we may be able to give better suggestions on how to achieve.

    Super stickiefied

    @snorklebum There have been changes to the heading elements used as previously in templates heading levels were jumped over causing missing levels non-sequential, however the results should have showed next to no change in terms of font-sizing, so perhaps you have overloaded the BP css styles or running a fully custom theme that just inherits templates?

    Profile photo of Hugo Ashmore
    Hugo Ashmore


    Hi @kenrichman We’re sorry to hear this, we are improving our accessibility on an ongoing basis.
    I can and will open a ticket for this issue and we’ll re-factor the widget markup however having had a quick look at this widget code we do adhere to expected standards i.e in providing labels & explicit label to input control linking, we don’t provide Aria attributes but these are not strictly meant to be used when html markup is correctly formed and described, we could add further title attribute to labels for screen readers to read but that is simply a supplement to the actual label text.

    It would help us if you could perhaps provide a little more detail on what Jaws is having an issue with, does it still have an issue if you switch to a simpler theme such as one of the twentysomething themes e.g. twentyfifteen.

    Profile photo of Hugo Ashmore
    Hugo Ashmore


    @mtgame21 We attempted to comprehensively provide classes on the body element to cover and catch as many conditions in BP so check those classes – as Henry points out – on the body element. The first you’ll possibly notice is ‘.bp-user’ to cover all instances of a users account screens. As an example if you’re looking at your profile screen you should see a series of body class tokens like this:

    xprofile bp-user my-account my-profile profile public buddypress

    With these classes we cover all important states, we inform we are on a Users series of screens ‘bp-user’, we state in this instance that it’s the logged in users account with ‘my-account’, we state the specific screen ‘profile’ and again we further specify that this is ‘my-profile’ the logged in user.

    Check out further screens to see how these class tokens will change.

    @dono12 Done!

    You don’t really need to be looking at that codex page, this ought to be a simple overload of templates, i.e copy register, from BP to your theme and edit as required. If you start to work with the extended advanced hierarchy templates you have to create full standalone templates i.e each must contain header and footer includes (hence why you appear to have lost styling, no head element for your document).

    This requires an understanding of the WP approach to template parts and creating child themes (if you’re not already running as a child theme) plus the BuddyPress template hierarchy as outlined in our codex.

    One approach would be to take advantage of the ability to call named template parts in WP so get_header() can become get_header('no-logo') which would then look for a file namedheader-no-logo.php

    A copy of header.php renamed to header-no-logo.php means you can now call a file that you can specifically modify – in this instance in the simplest terms you could remove any calls to rendering logos/backgrounds in this file.

    Running your BP templates in your theme or child theme (see the bp codex templating guides) would then mean you could run a conditional query to see if in buddypress.php which get_header() template to use by using a check for bp_is_user() but you’ll need moderate php skills for this.

    The better approach is to use the advanced BP template hierarchy which would allow you to create a file to act as index.php with all header/footer calls just for BP user screens.

    The easy or possibly easier approach but not one I advice is to do what you have mentioned you have tried in using styles to hide the elements.

    You’ll need a top level class identifier so we know it’s the BP screens we’re looking at and applying rules to:

    body.bp-user .logo-element {display: none;}

    I can’t advice what the correct selectors are as I’ve no notion of your themes structure, you’ll need to identify them and test until you find the right combination.

    Profile photo of Hugo Ashmore
    Hugo Ashmore


    @tranny I’m not sure I’m inderstanding the question or problem here, but if you want the styling for vert menu that would appear with no sidebars but do have sidebar in use you’re alternative option to the above solution provided by @airsid would be to ensure you have a copy of a primary temple i.e page.php moved to a bp folder in your child theme, in that you would use conditional checks around the get_sidebar() to remove it from loading on profile pages then copy the companion styles over and find the section for the navigation and where/how I select to show only if the class .no-sidebar is printed on the body element by adding in:, body.bp-user {} to all the rulesets that cover the navigation properties.
    ( I realise this is a not that straightforward though, and am puzzling whether we can write something better, but it’s a problematical area things like theme sidebars for BP and user account screens.)

    @airsid , @tranny

    We would need a little more detail to be able to help but are you running widgets in the main sidebar, i.e have you a right sidebar showing for your pages? twentysixteen will only set the vertical user navigation if there is no sidebar as the available width is too narrow so we drop back to the default horizontal navigation.

    Duplicate posts removed.

Viewing 25 replies - 1 through 25 (of 4,358 total)
Skip to toolbar