BuddyPress.org

Thank you very much. đoc truyện tại đây nhé

@danny80 did you go through the installation wizard after activating BuddyPress? https://codex.buddypress.org/user/setting-up-a-new-installation/installation-wizard/

it appears that every link, meta data etc (entire site map) is appearing at the bottom of my groups pages.

@mimip29 sidebar has dropped down below the content. You need to complete Step 3 of the BP compatibility process to a) bring back the sidebar beside the content OR b) remove sidebar and make the BuddyPress Groups/Members/etc pages full width.

Initial scan shows that you only need to create 2 files to make the BP page layouts fit with your theme’s layout.

If you want a page with a sidebar for BP templates: open up page.php, copy all code, paste to pastebin.com, click submit and post the generated URI here. Or if you want a full-width page for all BP templates, open up your theme’s full-width template and like page.php post the generated pastebin.com URI here.

closing duplicate of https://buddypress.org/support/topic/looking-for-a-sign-up-on-a-list-plugin/

@bphelp all the further requirements you want to add can be found in the various core files, I know no better than you at this stage and would have to be reading through those files to identify what functions, variables etc I had to work with to achieve what I wanted, I did something similar to this  a while back for  custom WP pages dragging user data out, the only way I managed that was by studying the core files.

Without wanting to sound harsh 🙂  it’s down to you to finish now, the bits like avatars shouldn’t be too hard to figure now you’ve got this far.

When it’s finished  get it placed on the WP plugin repo.

Seems like there should be an official place for such things and if not the codex then where?

Definitely a useful tip @umagokhale an issue that comes up quite a bit. Seems a bit odd your links are redirecting to customwebdesignseo.com even though you have already rebranded to 83 Oranges on the site and you obviously own both domains, but it is a nice looking site.

i think maybe we over thinking this a bit i don’t think @somdefabrica actually mentioned modifying any core files. Generally speaking there is no reason you should be afraid to update wordpress or plugins such as buddypress. It is always a good idea to make a backup (preferably in maintenance mode) prior to any upgrade or adding a new plugin or theme, just in case you have trouble or don’t care for the results.

Is there some reason you are afraid to upgrade specifically or are you just saying that upgrades are scary, generally speaking? If that’s the case i would suggest to you that not upgrading, especially with open source software carries it’s own set of risks. Generally speaking if you don’t want to upgrade something wordpress related you should have a very specific reason.

Try adding some more margin to the li elements in your toolbar because its uneven with the site name in the toolbar example add:
#wp-admin-bar li.no-arrow a {
margin-top: 3px !important;
}
Just a suggestion!

But how about users like me that already have a custom theme meant for buddypress 1.6.x? Will my template structure remain valid? Is anything going to be deprecated? Should I take some action or review my template?

Everything will continue to work.

And how about for people going to build themes for Buddypress?

We’ll need to write some codex documentation how best to do this 🙂

Have you edited any files that live in the directory:

wp-content/plugins/buddypress/

If you have then you will lose those changes if you do an automatic upgrade and have made a rod for your own back.

You will need to identify these changes and copy them to a child theme i.e copy the template files to the child theme where BP will use them in place of it’s own ones living in the parent plugin directory.

If you have made changes to any files other than actual theme files i.e core files then you have no option but to update and then manually copy those changes to the new files, but editing core files for any reason is never ever recommended and shouldn’t be done. Any changes a theme needs to effect can be done via hooks & filters via the child theme functions.php file or bp-custom.php file in plugins directory.

Or you could create a bp-custom.php which you place in your-site/wp-content/plugins
See:
https://codex.buddypress.org/developer/customizing/bp-custom-php/
And add this code:
http://pastebin.com/t9LybbQC
This is assuming you correctly targeted the element you want to change.

See:
https://codex.buddypress.org/developer/theme-development/a-quick-look-at-1-7-theme-compatibility/
and:
BP Theme Authors: make sure your theme registers 'buddypress' support

Just make a child theme it is really simple:
https://codex.buddypress.org/legacy/building-a-buddypress-child-theme/
If you make changes directly to your theme it will get overwritten upon updating.

Very minor changes were made. It should be safe to upgrade automatically.

If you’ve *edited* your current BuddyPress files, then this is a really good reason why it’s a bad idea to edit plugin files 😉

@chouf1 Ah right wasn’t aware of that prohibition on adding tips and code snippets, last time I looked there were a few. As long as they follow some form of best practise they ought to be ok.

On this basis “nor to learn how to customize it.” then to codex BP loops will need to be removed as they are technically customizations.

Thank you for your invite @umagokhale, but i’m already doing that on the french BP support since 4 years
http://bp-fr.net/groupes/comment-faire-pour/forum/

@hnla,

i added a page with tricks to the Customize Page a few weeks ago. Thinking like you it could be a good help to have such common tricks avaible from the Codex.
The whole Codex staff, included JJJ, fall over my head ! And the page was deleted  a few hours later.
Explanation was: the codex wiki pages are difficult to organize, code snippets aren’t always valuable over versions and by this, aren’t usage reference. The BP Codex is a reference, not a place to publish how to use it in concrete case, nor to learn how to customize it. Codex is codex and forum is forum. No comment. 😉

The only thing possible (allowed) to add on Codex is a link to a tread containing the trick. But not the trick directly. Why made simple when complicated can be done ?

Dura lex, code ex. 😀

How about adding some of these tips to the BP codex perhaps?

If you are going to leave links to your site please check those links are correct, also I would advise that you turn off PHP error reporting on a production server it’s really not very smart to announce to the world your server paths.

please report your bug on trac these support forums are not necessarily monitored actively by the folks that can actually do something about that.

https://buddypress.trac.wordpress.org/

@lchief What theme are you using as it’s managing to re-instate the bullets that the buddypress.css sheet removes using a pretty selective and specific ruleset selector group using the parent #buddypress id token.

Try adding this to your themes functions.php
http://pastebin.com/idRVTkAK