BuddyPress.org

@drdavis74 Per theme’s info page, Huddle already contains the necessary BP template files. So if you did activate BP template pack plugin and went through Appearance > BP compatibility process, then you could have overwritten the native BP files. In this case, re-upload the Huddle theme files to wp-content/themes/huddle/

@kookidooki WPMU is old school and has been merged with WordPress way back version WP 3.0. If you want to allow your users to create blogs, you’d have to create a Network (go Multisite) https://codex.wordpress.org/Create_A_Network

I would suggest deactivating BuddyPress and other plugins, plus changing to Twenty Eleven theme before creating a network. Please make sure that your multisite installation is working as expected before activating BuddyPress again. If you have any issues going multisite, please post at https://wordpress.org/support/forum/multisite

@ronnie_fantastic flattery will get you nowhere and this “legendary creature” cannot guarantee compatibility with Artisteer-generated themes. Having said that, we could give it a try. Do post the codes for header.php, sidebar.php and footer.php files as well.

@ouyagamingsource please create a new topic and move the information/questions you posted above which are not related to the subject matter at hand over there.

@ahmedselim open up your theme’s header.php file, copy all code, 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 files. Initial scan looks like you only need to create two files for BP compatiblity, but have to see the files first.

I would suggest you diasable all non essential plgins and possibly revert to the default BP theme to check things as you have a heavily moded site with plugins at worl and group slugs changed which might well be an issue.

It could just be that your theme has been customized not to show the activity updates/other details. Change to bp-default theme and check if issue is resolved.

1. If you’re LOGGED IN and go to the registration page, you will be automatically redirected to home page.

2. Did you enable registration in your General Settings?

3. What theme are you using? If a WP theme, did you install/activate the BP Template Pack plugin?

@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

@elmindo we’re going to have to hard code some of the template structures. Assuming that you’ve already set up your theme, let me know what your choices are in terns of
1. theme version you used: Full Width OR Boxed? Which one?
2. sidebar for ALL BP templates: No sidebar (full width) OR Left Sidebar OR Right Sidebar OR Both Sidebars? Which one?

@stefan83

1. What theme are you using? Did you apply the HTML changes you made to the other BP component changes to your register.php file? Site URL?

2. please do not make any changes in core files “plugins/buddypress/bp-themes/bp-default/registration” as those will be overwritten when you upgrade BuddyPress.

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’);

If you can target that element using a development tool like firefox’s firebug then you could use css trickery to make it disappear. Example:
#a_div {
display: none;
}
That is probably the least destructive way to get rid of it in a child themes style.css If you wanna change the label then use a language file. Its super easy and also is not destructive:
https://codex.buddypress.org/extending-buddypress/customizing-labels-messages-and-urls/