BuddyPress.org

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…[Read more]

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…[Read more]

@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…[Read more]

@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…[Read more]

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')…[Read more]

@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…[Read more]

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

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…[Read more]

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…[Read more]

It’s by design:
https://buddypress.trac.wordpress.org/browser/trunk/src/bp-templates/bp-legacy/buddypress/members/single/messages.php

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…[Read more]

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.

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.

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…[Read more]