BuddyPress.org

Ah ok had forgotten about that thread, I’ll perhaps make a sticky thread outlining those steps so it’s a little clearer.

Have either of you contacted the theme authors before asking here?

Notifications was a new component in 1.9 if template files are overloaded as they are with CC then modifications need to be made to /members/single/home.php and dir added for the template include parts, only themes that run under theme compatibility or use bp-default directly…[Read more]

What changes? There aren’t any real changes to template files.

To avoid losing custom work to template files one should always be working in a child theme or a theme that has had the bp-legacy template files copied over to run directly in the theme i.e overloading the files BP uses from it’s core template files.

You may need to explain exactly…[Read more]

But sounds as though this needs looking into further in respect of checking for BP standard components so a ticket might be appropriate in trac.

WordPress was designed just so that people who didn’t know how to code could build custom blogs and websites.

No it wasn’t actually, it was originally just developed as a blogging app to be better than those that existed, and in the early days before the theme api or the plugins api were introduced you would have had to have some knowledge of b…[Read more]

Try logging in as one.

Unable to replicate any issues either creating new or updating group avatars on 3.8/1.9.1 WP single site.

Although it doesn’t sound like a theme issue it’s always advisable to change to a standard WP theme to double check if issue present if of course you haven’t already.

> I’m conflicted on how much we can realistically support themes that deviate so far from the norm.

I see no real conflict to be resolved, it’s impossible for BP to take into account unknown divergences from the core template api WP provides, if theme authors want to create something non-standard then sadly that’s their problem and unfair to e…[Read more]

Sounds as though having another item labelled ‘members’ caused BP some issues, but hard to say for sure without lokking deeper into the code and testing things.

Of course you can, and then instantiate your own theme_compat class if wished or just run from the root themes functions.php.

NP

Codex is your friend – https://codex.buddypress.org/getting-started/customizing/bp_enable_multiblog/

Cool, it’s why we wanted that hierarchy 🙂

What is the condition under which this will be called into play? Have you looked at the codex, read the theme compatibility guides on using custom templates based on group name. action etc that way you can have templates to suit certain conditions calling diff header files if necessary.

Also please bear in mind some of these requirements are going to require some coding skills, you have a quite a few custom requirements which are going to be beyond the scope of the forum to provide simple answers on. Some aspects such as frontend posting may be served by third party plugins such as bp-simple-front-end-post though.

You need to update your WP/BP versions don’t lag behind important updates/changes and security fixes.

As for the issue, first place to start is with any plugins start deactivating to see if one of them is causing the issue.

I can see that bp classes are added to markup so BP is in action, that the BP content isn’t rendered suggests that the themes page.php breaks the WP process BP relies on, you have tested by reverting to a theme that works to see if it’s a theme issue haven’t you?

@modemlooper the reference was to the theme being looked for in WP repo or at least in general searches and in that sense an official standalone theme release which is what it will need and ought to be eventually. Well done though for getting that out there; we can link people to it who are worried and want to get ahead of the game.

and ensure you are using some form of server side compression i.e on Apache mod_deflate that will make far more difference than trying to minfy any client deliverable files, don’t mess with inline comments or human readable formatting if possible.