BuddyPress.org

Use this plugin: https://wordpress.org/extend/plugins/buddypress-registration-groups-1/

@ouyagamingsource to make your Alyeska theme compatible with BuddyPress, you need to install/activate the BP Template Pack plugin, the go through Appearance > BP Compatibility process as you’ll see https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/

You’re in luck, we’ve helped another person some months ago with Step 3 for the Alyeska theme at https://buddypress.org/community/groups/installing-buddypress/forum/topic/customising-alyeska-theme-for-buddypress/

If you have any issues re Compatiblity Process, please post at that thread.

== I am not sure if i can get away with the creation of the three “-buddypress.php” files or if I need to modify the 16 files and which code I need to copy. ==

@ahmedselim IT all depends on the HTML structure of your WP theme. You just cannot copy the code given for other themes because each has distinct structures and in all probability, not applicable to your theme’s. Have you looked if your theme is listed among the template-packed themes at https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/#template-packed-wordpress-themes

I already have a plugin my friend and it is free.
https://wordpress.org/extend/plugins/buddypress-friendpress/
I can customize it to your liking for some beer money lol!

Then check the other fields. Here is a copy of one of my local sites wp-config.php:
<?php
/**
* The base configurations of the WordPress.
*
* This file has the following configurations: MySQL settings, Table Prefix,
* Secret Keys, WordPress Language, and ABSPATH. You can find more information
* by visiting { @link https://codex.wordpress.org/Editing_wp-config.php Editing
* wp-config.php} Codex page. You can get the MySQL settings from your web host.
*
* This file is used by the wp-config.php creation script during the
* installation. You don’t have to use the web site, you can just copy this file
* to “wp-config.php” and fill in the values.
*
* @package WordPress
*/

// ** MySQL settings – You can get this info from your web host ** //
/** The name of the database for WordPress */
define(‘DB_NAME’, ‘bpdev’);

/** MySQL database username */
define(‘DB_USER’, ‘root’);

/** MySQL database password */
define(‘DB_PASSWORD’, ”);

/** MySQL hostname */
define(‘DB_HOST’, ‘localhost’);

/** Database Charset to use in creating database tables. */
define(‘DB_CHARSET’, ‘utf8’);

/** The Database Collate type. Don’t change this if in doubt. */
define(‘DB_COLLATE’, ”);

/**#@+
* Authentication Unique Keys and Salts.
*
* Change these to different unique phrases!
* You can generate these using the { @link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
*
* @since 2.6.0
*/
define(‘AUTH_KEY’, ‘gKR[~e-<4 |Jj1DVfT-RM.m(|=M7(OB;tp/bfQt9+9[+FcIK<Gdp[(*u~2@-_H*J');
define(‘SECURE_AUTH_KEY’, ‘_$y7AKT$.Zz`XHS3 DxndhyLGd/3ITTfE3oJqphSGS:x1*TH@45D 6NIjU7y64om’);
define(‘LOGGED_IN_KEY’, ‘i6[pr$z#c,0E&EI]j]:K}cG9N`J[:JsL]wgy%[coeV>h(<c#W%Ye');
define(‘NONCE_KEY’, ‘@GH9@ITlC&Py&cG3O5sKaVrm;vqP/4mKYz#=n>K?`%:C.q56yFO4WEaY:g^Rs+>+’);
define(‘AUTH_SALT’, ‘QulXiJdP`zXXz*D*]RbfXfH[$C6 Z;:n>pLwcrSZvkY!7|*mHxyS>#n^qqiD2noO’);
define(‘SECURE_AUTH_SALT’, ‘3/{(F|iduMA;QfF%OPY:jHTH:D8jcmWB&h`gfs$K4L&uTVhg1.05nz~h.COtvf+7’);
define(‘LOGGED_IN_SALT’, ‘YG?P2/ <+A,W8L:r<0^9~n1c<aO-w|OTl~.o^T39ZPp)tz7&V~[x57X&n,(*(iA0');
define(‘NONCE_SALT’, ‘|G0,AO(>,Ak @y a/A;Kf3it9W~Lv[/q*?,Pe!Dqf~WDzKzD?JJQ+V%.:]icGtzq/’);

/**#@-*/

/**
* WordPress Database Table prefix.
*
* You can have multiple installations in one database if you give each a unique
* prefix. Only numbers, letters, and underscores please!
*/
$table_prefix = ‘wp_’;

/**
* WordPress Localized Language, defaults to English.
*
* Change this to localize WordPress. A corresponding MO file for the chosen
* language must be installed to wp-content/languages. For example, install
* de_DE.mo to wp-content/languages and set WPLANG to ‘de_DE’ to enable German
* language support.
*/
define(‘WPLANG’, ”);

/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*/
define(‘WP_DEBUG’, false);

/* That’s all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined(‘ABSPATH’) )
define(‘ABSPATH’, dirname(__FILE__) . ‘/’);

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . ‘wp-settings.php’);

Nice list. Can I recommend @modemlooper ‘s extended settings plugin:
https://wordpress.org/extend/plugins/buddypress-extended-settings/
And BP FriendPress:
https://wordpress.org/extend/plugins/buddypress-friendpress/

I just noticed a comment about BP FriendPress plugin. The answer is yes it is still supported. The stars rating system on here does not work accurately because there is no way my BP Buddybar back is scoring higher than my BP FriendPress plugin so instead of looking at stars go on WordPress and search for support for the plugin. If you see no support issues it is a good sign the plugin functions correctly.

Please please stop posting this on multiple topics. If you haven’t had a reply yet, it means no-one’s sure what the fix is.

How did you install BuddyPress? What versions of WordPress and BuddyPress are you using? Do you have a bp-custom.php file (if so, what’s in it)?

Turn resend.php into a page template and place it in your theme folder. create a page and attach the page template to it

Please submit a ticket to https://buddypress.trac.wordpress.org/

@dyst4f Based on the HTML structure of your theme, you need to change 16 template files within the 6 BP folders transferred to your continuum theme folder in server during the compatibility process.

Try @modemloopers plugin:
https://wordpress.org/extend/plugins/buddypress-extended-settings/
By the way I need a prayer request so I am interested in your site.

Edit:
I am not trying to personally attack you but there is a pecking order and you have not earned the right to charge for a plugin yet. I program stuff like this while I am asleep so I have no use of your code other than testing it so non-programmers may benefit. People I respect are @mercime @hnla @r-a-y @djpaul @boonebgorges @johnjamesjacoby They never charge for helping a soul.
Your a developer just like me so please do not use the word “we” to address me. You are an individual trying to sell a single plugin with with no credentials at all so don’t mislead people into thinking your some big corporation by using that word. Its condescending to speak to a fellow developer in that manner. @modemlooper has already made plugins free of charge and he has a ton of experience more than I have, and probably more than you as well. His plugins are solid so I am inclined to give links here for the sake of open source:
This is a awesome plugin for free:
https://wordpress.org/extend/plugins/buddypress-profile-menu/
This is another awesome plugin for free that allows you to do many things including changing order of buddypress profile items among other things.
https://wordpress.org/extend/plugins/buddypress-extended-settings/
All credit goes to @modemlooper for his dedication and contributions to open source software. @r-a-y also has some awesome plugins that still are functional.

Yes that is the latest version. See: https://wordpress.org/support/topic/plugin-bp-adminbar-for-admins-only-extra-space-after-php-closing-tag
I cant see any white space but maybe I am overlooking it.

did you use the one click WordPress installer? If so, delete it all a install WordPress manually

The BuddyPress Custom Profile Menu plugin should really help you out with this: https://wordpress.org/extend/plugins/buddypress-custom-profile-menu

(full disclosure: it’s our plugin )

The BuddyPress Custom Profile Menu plugin should really help you out with this: https://wordpress.org/extend/plugins/buddypress-custom-profile-menu

(full disclosure: it’s our plugin )

See http://wordpress.stackexchange.com/questions/66204/showing-the-users-username-in-registration-email-or-activation-page-with-buddyp

Hey! for BP 6.1 :
Lous thinking!
Working on the same problem. Maybe try this advice. The problem is; you cant send private not-friend-messages or mentions or scale up to blog-user-based systems with whitepaced usernames. In the end the user gonna need to enter no-whitepace-names. So interacting nicely would be better approach:

1) To accept the user to type whitespace, but not record them, using jQuery
2) Use EMAIL also to login https://wordpress.org/extend/plugins/wp-email-login/

Example for 1) :

– Leave the register process AS IT IS in bp 6.1 -as now accepts:

Donald Duck = donAld duCK = or HOWEVER a user choose their username with lowercase/ uppercase (This is good for loggin back in – many forgot their cases). The username avabililty checker don alows any other combinations either by default (DonaLD-DUCK is occupied).

– Run a jQuery on(‘keyup’) function as a validator when form appears at :

a) register
b) Loggin in
c) Changing username (if enabled by any plugin)
d)* Display name (xprofile required field) = profile edit BASE submit

OBS : The keyup replaces any whitepsace on the fly when user typing in their Username with hyphens. Diffrent browser handle this diffrent, so a onfocus need to be provided if user PASTE their name. NOTE : YES The user with no javascript has to look at the instructions instead …

The results will become : “Donald-Duck” as username, loggin in however letters cased.

If you don wanna show this white-space replacement, Use ‘onsubmit’ instead of keyup -so it can be added silent. But I think its better to LEARN the user to use Hypens – by see the “forced action”. The user will need to write correct usernames when sending/ composing messages and mentions and feeds and…if you scale up.

GOOD: “donald-duck” as the sitewide username = key (private messages, mentions and slugs for blogfarms etc etc)

Also – for user exp – Use a tooltip to make it CLEAR that we are replacing their favorite username with hyphens.

* Display name field, change in the template to ‘hidden’ in xprofile situations. Menaing: NEVER let the user be avaible to fill that out. So the trick comes to the register process. This field is hardcoded required. Let the field be hidden by CSS, added a clone of Username field in the submit. Let the username be Masterfield so avabililty check running ok. Then you get rid of Display name showing SAME for diffrent users – if they can type by themselfs.

Special if you dont wanna display/ using First and Last names:

I have hidden the Display name field in register/ everywhere, cloning username data on Submit, splitting hypens so it displays Donald Duck.

In the payment forms Firstname = Donald Last name = Duck
OTHERWISE the first name will be Donald-Duck and last name Empty.

Summary:

Don mess with php tweaks so urls get crazy, you loose quality of your collected database if ya cant scale up or migrate in the future. I tried everything and belive me, a small site will starting have problems very soon. Don core files, its security reasons why no filtering is easy to do here – I suppose, after trying everything with authenticate filters and hooks.

I woluld like a plugin to Change ALL custom messages provided in the sign up processes in WP. Including The boring email without username provided. The Welcome Pack can do this with some trix. So the user-name is shown in confirm message.

/ Hope it helps.