Skip to:

Forum Replies Created

Viewing 25 replies - 1 through 25 (of 4,341 total)
  • 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.

    Just seen your response:

    >To be honnest I haven’t a regular licence for this theme so I cannot expect technical support.

    And we are limited in the help we can offer on premium themes sadly.

    Those look to be modified files, not the copies from the BP core plugin, the cover-image-header.php file appears to be missing some elements necessary.

    Again as my earlier comment have you asked this question of the themes authors, you need to as we can’t really support third party custom work, if they find that there is indeed an issue with the core implementation then we’ll definitely look into it.

    Also you could look to test things by ensuring you are running a copy of the files taken from the core bp-templates/bp-legacy/buddypress/members/single/ directory.

    Have you asked this premium themes authors/developers about this issue?

    While there may be an issue we haven’t spotted, setting up to try and reproduce is somewhat time consuming so it would be good to have acknowledgement from the themes devs that this isn’t an issue that needs dealing with in this theme rather than with BP core implementation.

    Can we be clear what theme/buddypress/css/ refers to is this a reference to the core BP plugin or is this a BP ready theme that you are running a child theme from?

    Cover image styles are loaded as ’embedded’ ( styles written to the head of a document within style tags) styles so not a mystery 🙂

    In a help thread you are meant really to attempt to describe a problem, not simply post a SC.

    If you want to know whether this is theme related then you activate one of the default WP twenty* themes and establish whether the issue still exists.

    @hastig While it is genuinely appreciated that you are trying to help people, some of what you are describing as template files is a little confused and will mislead people into thinking they have to use the advanced taxonomy template hierarchy which isn’t necessarily the case.

    I’d urge you check our codex pages again to best understand how overloading files works.

    The stackoverflow page would be better removed or at least edited to better reflect how the BP template hierarchy works.

    It’s by design:

    Closing php tags shouldn’t be necessary, WP instructs not to close out files in this way. If you’re having issues they must lie with the custom templates?

    I would ignore the “warning” and move on, the form ‘action’ attribute is not explicitly set as required, browsers will work without it being set and return the existing url; personally I prefer it set but…

    I would take care in running validation routines over WP code, you’ll almost certainly receive a lot of warnings from various areas and given most sites are built on a structure of modular third party code, it will be next to impossible to get 100% clean results.

    Profile photo of Hugo Ashmore
    Hugo Ashmore


    For why?
    What’s the issue you’re having?

    You should have control of your templates now and can modify as you need; the master WP template that would be used is generally page.php copy that to /buddypress/ and rename to buddypress.php to have control of this top level template.

    Profile photo of Hugo Ashmore
    Hugo Ashmore


    You have third party plugins at work here and one of those is causing the problem, ID the plugins, attempt to isolate the culprit ad report to plugin author.

    Profile photo of Hugo Ashmore
    Hugo Ashmore


    Explain in detail! Exactly what file, copied from where to where and in what directory structure is it housed in the new theme location – there is no one index.php for BP and all files, if we’re talking theme compatibility, are NOT standalone template files despite the implication in naming i.e ‘index.php’ but are themselves just partials that get injected into the WP template API via the title & content tags, check the BP template hierarchy guides.

    Profile photo of Hugo Ashmore
    Hugo Ashmore


    @jblevins1991 Please check through the BP codex documentation we provide a few guides there that set out how BP templating is structured and how to overload the files to a theme or child theme, this is your first port of call for information thereafter if you still have questions not covered in our guides do ask back here.

    If you are taking this topic to a private channel, then this topic will be closed. Please remember that public forums are intended for open topics where the help may benefit others, also the referenced issue is a third party plugin, not BuddyPress the correct avenue of help would be the plugins WP support forum normally.

    @ldesherl I think it might help if you could leave that link above switched to a WP default theme and with all plugins deactivated, just while you’re seeking help for this issue, as things stand I see no sight of BuddyPress or bbPress running, and the theme is a custom one with a lot of plugins running. Buddypress should default to using a series of pages that it will create, your ‘Activity’ example is named with a custom title, you also seem to have a lot of trashed pages as the members page slug has ‘-7’ added suggesting 6 other copies of a page named ‘members’ try deleting those.


    …but I just feel like the codex should not be so freaking skimpy and weak.

    Then please help to make it better! As mentioned BP is a voluntary project representing many many hours of freely given time by the core dev team and various contributors. The codex is something that takes a massive amount of time to organize and update, myself and mercime have given a lot of our time, over the last two years to trying to update and better organize the codex, help is always welcome though and aspects like the codex are only as good as the time the wider community are willing to put in.

    You can do anything more or less with a little styling.
    Just remove the left margin on .activity-comments, but observe how that affects them in all screens and taget specifically, the body element generally carries useful classes to use.

    @jblevins1991 You need to explain exactly what you have attempted so that we may understand where things are going wrong, so you need to show exact steps and directories and files created / copied over.

    Assuming you have setup WP and BP correctly and have a vanilla instance of BP running under a theme of your choice then:

    You create a dir or folder in your themes root e.g /buddypress/ if you want to modify the main activity screen then create /buddypress/activity/ and copy index.php from the plugins bp-legacy dir to this new directory, add some text somewhere in that file so you can see if BP is using that file rather than the version located in bp-legacy.

    In our guide the salient issue of what templates and where is covered in this paragraph:

    Therefore, you can modify any bp theme compatibility template by copying it over from:



    /my-theme/community/ or /my-theme/buddypress/

    N.B. Inside the subfolder ‘community’ you must preserve the path structure/folders that exist in the BP original /buddypress/ folder so /activity/ must be created to hold index.php or any of the other activity templates.

    If you are using a WP theme or theme that is subject to updates you must create a child theme of that theme and do all work in that, this avoids you losing any changes in a theme – guides for creating WP child themes are available on the WP codex.

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