BuddyPress.org

@mumbaipav Based on the HTML structure of your theme, you will be only need to create two new files, header-buddypress.php and sidebar-buddypress.php to make the BP templates compatible with your theme.

If you’ve revised any of the BP template files transferred to your snapwire theme folder in server during the BP Compatibility process, please delete the 6 BP folders transferred to your snapwire theme folder in server – /activity, /blogs, /forums, /members, /groups, /register – then re-run Appearance > BP Compatibility again to make sure that you have clean template files.

A. COPY your theme’s header.php and Save As > header-buddypress.php

Open up header-buddypress.php and at the BOTTOM of the file, below other code contained within, add this:
`

@peppermintmochapatty if you are using this theme, https://wordpress.org/extend/themes/first-lego-league-official , you cannot use the second method (creating xxx-buddypress.php) for Step 3 of the BP Compatibility process. Because of the HTML structure of your theme, you’d need to revise 16 template files from the 6 BP folders transferred to your theme’s folder in server.

If you still want to proceed with the instruction, let me know.

Oups ! Also missed ” I’m asking for another alternative instead of plugin as use the function.php.”

Try with this in theme’s functions.php
`function my_member_username() {
global $members_template;
return $members_template->member->user_login;
}
add_filter(‘bp_member_name’,’my_member_username’);`

well I am using my own theme

http://transformers.scifi-guide.net/

@davidkooo – which theme are you using? I noticed one ‘off the shelf’ theme was adding additional profile field links – in which case you’d have to strip them in your templates as well.

Just to clarify, what is the official FLL theme? If you meant the BuddyPress Default them you do not need to add BuddyPress capability – it comes with it.

Hello,
what is your mother language ?

If you use define(‘DOMAIN_CURRENT_SITE’, ‘buddypress.seyte.com’); it means that “buddypres”s is a subdomain of seyte.com !
This suppose also that wordpress is installed at the root of seyte.com.
But you declare define(‘SUBDOMAIN_INSTALL’, false);
Pass this to true instead of false and see what you get.

Subdomain install needs also the usage of a wildcard declaration on your host settings.

https://codex.wordpress.org/Create_A_Network
https://codex.wordpress.org/Before_You_Create_A_Network

If this is too complicated for you, i suggest that you deactivate all your plugins and custom theme.
Erase the wp-config file and restart your WP install. Be sure that wp is at the root of seyte.com
After this install, go to wp-admin and activate the network install.
When done, activate the buddypress plugin.
Make the setting of BP specially “blogs” creation.
Activate bp-default theme and test your install.
If everithing is working, create a new blog and test again.
Now if you want you can change the themes of the main site and/or the newly created blog.
And finally reactivate your other plugins (if you use some)

Yo, i understand your frustration, but debuging by the “common way” is the first thing to do.
If your install worked before upgrading and no more after, it’s logical to think that there is somewhere a conflict or a missing piece of code.
Custom themes and plugins are mostly the culprit. JS sliders, plugs with text editors are also common sources of problems.

There is no universal answer. Each site is different, each problem too.
I recently get a blank page because of a missing > in one of my template loop !
I updated to 1.6.1 and all my pages disapeared and i had to recreate them one by one.
After 4 years of BP usage, it’s just an incident. But i understand, especially it it’s the first time you run such a trouble, how this can be annoying, for sure !

On this topic, you claim all “it’s no more working.” but no one said what he did, what theme he use and what type of install he manage. All these details are missing in this topic. And so far i know, nobody here is a soothsayer. I’m not.

Other common forum user behavior: no or less feedback when a solution is found. So coming here and saying “it’s not the problem” after an answer, is not fair. If it’s not the problem, why do you ask for help ? And if it’s the problem, why don’t you explain it ?
Pages are gone is not the probleme description, it’s the problem RESULT description.

A clearly explained problem brings to a clearly solution.
I don’t know what happens for you. I only try to help you with common questions intented to guide your debug search.

Let me suggest you that if you want to know what 1.6.1 did, go to the trac and compare the version changes. It’s very easy to find this information on the Trac. But you have to read the code.

If “it’s not the problem” with common guidance as read above, may i suggest you to activate the debug mode in wp-config file. Perhaps some warnings or server information will help you further.

Sorry it’s also a common help answer. And as i’m french, sorry for my poor english.

The time spent on running all the filters and actions is negligible, really. And if you need the extra functionality a plugin provides, then it doesn’t matter if you include the code as a plugin or include it via your theme’s functions.php file. It’s got to get loaded anyways. The only difference is the time when it gets loaded.

Personally, I have a look at the code before I install a plugin for the first time. Nicely formatted code and proper in-code documentation give you a good first impression of the code you’re about to run. Of course, to most end-users this will only be goobldygook, but there are tools out there. YSlow, Debug Bar Console, etc. Then there’s plugins that monitor the load time and can give you detailed information about the load times (had a quick look for one I sometimes use, but couldn’t find it).

I’m not a Buddypress developer, but I am advising my users to only use their first name, nickname, or username for the “Name” field. On the other hand you could try removing some of the related script in register.php which controls the content on your Register page. The file can be found under wp-content/plugins/buddypress/bp-themes/bp-default/registration/register.php. Just make sure you download the file or back it up before modifying and testing the file.

My first though is have you updated all your plugins and theme (if there are new updates) to go with your BuddyPress install.

Secondly, have you re-saved both your permlinks and settings under BuddyPress – that would be through the admin?

That’s a ton of scripts. My bet just by looking at it is the Nexgen is slowing things. Check these out….

Only loads Nextgen on pages where it is used:
http://www.markstechnologynews.com/2012/02/nextgen-gallery-optimizer-wordpress-plugin-helps-boost-your-sites-page-load-speed.html

Optimizes images:
http://shanebishop.net/ewww-image-optimizer/

I would limit the number of images in your slider and other basic steps. You should also limit the number of widgets you use. It’s hard to tell just by looking at what you posted. Not sure what type of theme you are using, but unless you built it yourself or are using the default theme I would bet it extremely bloated like almost all premium themes sold today.

@travel-junkie It’s a myth yeah, but it’s not a myth that at each page load, the page is recontructed with all the plugins, filters, filters of filters, and all the rest. The amount count or better said the server settings of many details such as php memory, max_exec etc

You’re right, good coding practice is the primar condition, but who knows that when installing a plugin ? A quality plugin coded under the 4.x area isn’t really quality satisfying today. Awfull plugins writen with the feet, but doing the job (even if penibly) are(where) legion.

Most of the plugin’s user are not php guru’s to see what changed, what is good or not in the code.
Even pro developper’s are not all qualified to be quality dev’s. Go, go, go, allways faster und hektische arbeit zum schluss. You’ll probably know that.

And what is “quality” in the wpsphere ? 5 minutes install, download a theme, a plugin by one click and bum, done ? In the best case, user will shout “it work’s !”
It’s not quality, it’s just an easy craftwork.
Aber sonst alles klar. Tchuss

EDIT: a funny conclusion to this just posted here few minutes ago in this tread:
https://buddypress.org/community/groups/creating-extending/forum/topic/bp-better-directories-abandoned/
that mentionned this (very explicit in my mind)
https://wordpress.org/support/topic/plugin-bp-better-directories-ready-or-not

Use CSS to do this. Add to style.css file from your child theme.
For groups avatars:
`div.item-avatar img {width: xx px;}`

For users, it depends of the place you need that. You have to search in the source code.
For ex, the avatar near a topic answers, use
`div.poster-meta img {height: xx px;}`

Read again @frank13 ‘s answer.
You have to make a copy of post-form.php file and put it into your church theme
From within this copy in this copy you comment the line 25, like this
`// printf( __( “What’s new, %s?”, ‘buddypress’ ), bp_get_user_firstname() );`

Done !
I you ask again i will answering in french

I’m using the Genesis frame work with the church theme. What do I exactly have to do to disable “what’s new” in profile?

Upload the whole bp-default theme manually via FTP.
If it’s OK with the default thme, do the same with the original files of your custom theme.

Control also that you have a page for each bp page.
After updating to 1.6.1, my pages where all lost and i have to recreate them…

the loop is in the file called profile-loop.php
buddypress/themes/bp-default/members/single/profile/

To work on it you have to create a child theme first or you will loose your modification at the next update.
You can download the modified file from here: http://bp-fr.net/wp-content/blogs.dir/1/files/group-documents/24/1345718022-profile-loop.zip

hi,

as you can read here https://codex.buddypress.org/releases/version-1-6/ in the Profile Field section, since BP 1.6, each user can set his profile fields to different visibility option from within his profile option admin.

You can also modify the template profile loop from a child theme to avoid site wide not registered users to see profiles unless they are logged in, by adding the contionnal tag if bp_user_is_logged_in.
Add this just after the first line containing do_action and don’t forgot endif at the end of the page, just before the last do_action.