BuddyPress.org

Links like these any good? Not sure if we can manipulate the trac download URLs: https://buddypress.trac.wordpress.org/changeset/HEAD/tags/1.5/bp-themes/bp-default?old_path=%2F&format=zip

If anyone wants to talk about issues other than 1.6-RC1 in this thread, please make a new thread. Let’s keep this one on topic from now

Yo! Did you fork this? I’m just about to customise those 16 theme templates, and I’m just not sure where to edit the templates exactly.

Glad you resolved this on your own. For others, add “buddypress” without the quotes to tag in stylesheet.

`Tag: buddypress, etc. etc. etc.`

@idanny08 open up the header.php of your wisdom theme, copy all, paste in pastebin.com, click submit, and post the generated URI here. Do the same for your theme’s index.php, page.php, sidebar.php and footer.php

Initial scan shows that you might just need to create only two files to align HTML structure of template files. But we need the information requested above to help you.

It seems that your theme has changed things around from ‘normal’. What theme are you using?

One would expect the file ( and line number in bp-default ) to be like: https://buddypress.trac.wordpress.org/browser/tags/1.5.6/bp-themes/bp-default/registration/register.php#L68

If you have a utility that will search with ‘Find in Files’ such as is available in notepad++ then you might be able to find where it’s been moved to….

BOOM! https://codex.buddypress.org/releases/bp-default-theme

Is there a place to upload zips of just the theme? Here maybe? bp.org/download/theme ?

I want to add direct zip download link.

This should be a new topic but I agree with Roger. I think BP-default should be on WordPress.org. I’ve had on many occasion needed an older version. It also gives users an indication they can use another BuddyPress theme from .org. I would even go as far as not bundling BP-default and only use .org. It’s easier to delete a theme when beginners mess up code and download via .org than to mess inside /buddypress

I will create codex page. We need a discussion about the theme changes in 1.7 so it will be done properly to benefit the community. I know there is talk of using something like bbPress but I have struggled to understand its method and this is not good for designers who are not as good with php

If you want to add code to this site please use backticks to add as otherwise we can’t see it.

Alternatively please use something like https://gist.github.com/ to provide a link to your code. This is a better method in my opinion and also helps if you have a large chunk of code you want to get opinions on.

I’d like to check what you are trying to do here if that is ok. Are you trying to add pages to the entire BuddyPress site or just show extra pages when on the directory pages eg; members, groups? Or are you adding page templates to the theme directory for BuddyPress?

This is why beta/RC testing helps us identify areas that we’ve inadvertently broken, so we can address any regressions.

Other argument: why can’t we make minor changes to the theme? In 1.6, we’ve made some JS and CSS improvements to allow parts of those things to be more easily overridden by child themes. I think that’s the extent of the changes, though I can’t remember until I/we write up the release notes.
Functionality hasn’t changed. The more drastic theme changes in the old 1.5 did cause some upgrade complications, and we’ve learnt from that.

The themes are versioned. I don’t believe CSS/JS tidy up merits a “new” theme. If/until BP-Default is put on WordPress.org’s theme repository, if someone wants to make e.g. a codex page with links to .zip of BP-Default from each BuddyPress, go for it.

At any rate, we all know the pain points in building a BuddyPress theme based off BP-Default at the moment. Future releases of BuddyPress won’t ship with a theme, so this problem will eventually go away.

Guys – bp-default shouldn’t change with every release of BP, particularly if you’re encouraging people to build child themes off it.

If you want to change look and feel of the default theme packaged with BP, you should release it under a new name, pretty much as WP does (kubrick.. default.. twenty ten… twenty eleven). Then when a user upgrades the core, their site will continue to look and feel just the way they intended it to.

If, because of the nature of BP (regular new features), you’d also like to offer a parent theme that grows with each release, then OK — offer that as a second option — but label them clearly.

Need to finish writing the change log too

@mercime We’d have hope theme authors were testing their themes when we were in beta — but if you find any regressions in BP-Default in RC, please raise trac ticket

BP/WP versions? Are you using the bp-default theme or another theme?

You’re welcome @timetraveler – Marking this as resolved.

@gswaim as I see it, the theme dev intentionally made the BP pages full-width.

Initial scan shows that you’d have to revise around 16 BP template files within 6 BP folders included in your supermassive theme (I assume they are bec. dev said it was BP-ready) to change the HTML markup and add style classes as well as sidebar to the BP pages. Not sure whether you’d have to pay the theme dev to provide the revised pages or if he/she would provide revised template files for free.

Thank you @boonebgorges First tests looking good except for a couple of my custom bp-default child themes

Have to update BP Codex on new Activity Stream panel, group/sitewide forums, etc

Hi Auktweena — that plugin is not related to BuddyPress, so you would be better off asking questions on the forum for the plugin, or on the wordpress.org forums.

As for step 3 – that’s standard ‘stuff’ for integrating a plugin’s templates into the theme you’re using for your website. This article gives you an introduction to theme development in WordPress: https://codex.wordpress.org/Theme_Development

Generally, theme work requires PHP development experience. In your case, to get the basics up and running, it looks like you just need to copy some files… you’ll need an FTP client to navigate and copy / move around the files on your website.