BuddyPress.org

Thank you my problem becomes solved.

Best regards

So I think I found the part that creates / modifies the excerpt. It is in bp-core-template.php. Starting at line 353.
`/**
* Truncates text.
*/
function bp_create_excerpt( $text, $length = 225, $options = array() ) {
// Backward compatibility. The third argument used to be a boolean $filter_shortcodes
$filter_shortcodes_default = is_bool( $options ) ? $options : true;

$defaults = array(
‘ending’ => __( ‘ […]’, ‘buddypress’ ),
‘exact’ => false,
‘html’ => true,
‘filter_shortcodes’ => $filter_shortcodes_default
);
$r = wp_parse_args( $options, $defaults );
extract( $r );

// Save the original text, to be passed along to the filter
$original_text = $text;

// Allow plugins to modify these values globally
$length = apply_filters( ‘bp_excerpt_length’, $length );
$ending = apply_filters( ‘bp_excerpt_append_text’, $ending );

// Remove shortcodes if necessary
if ( $filter_shortcodes )
$text = strip_shortcodes( $text );`

`remove_filter( ‘bp_create_excerpt’, $length, $options );
function pnb_excerpt(){
$lenght = 500;
$options = array(
‘ending’ => __( ‘ […]’, ‘buddypress’ ),
‘exact’ => false,
‘html’ => false,
‘filter_shortcodes’ => $filter_shortcodes_default);
return apply_filters( ‘bp_create_excerpt’, $length, $options );
}`

I also tried with apply_filter, and without the remove_filter.
How do I overwrite the defaults? (The $length, and the $options array).

Thanks in advance,
Ruud

Yes,

I did the steps written in this link only, https://codex.buddypress.org/user/buddypress-site-administration/deleting-buddypress/.

But issue is still there. Also, one thing is that in my admin panel I can see that multisite is disabled, while I’ve enabled it in wp-config.php
Is this could be the issue? If yes, then let me know how to remove this thing.
Have a look on my wp-config.php and let me know your feedback. Removed original credentials.

`
<?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', database name);

/** MySQL database username */
define('DB_USER', user name);

/** MySQL database password */
define('DB_PASSWORD', password);

/** MySQL hostname */
define('DB_HOST', 'dbp12.meebox.net');

/** 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', 'put your unique phrase here');
define('SECURE_AUTH_KEY', 'put your unique phrase here');
define('LOGGED_IN_KEY', 'put your unique phrase here');
define('NONCE_KEY', 'put your unique phrase here');
define('AUTH_SALT', 'put your unique phrase here');
define('SECURE_AUTH_SALT', 'put your unique phrase here');
define('LOGGED_IN_SALT', 'put your unique phrase here');
define('NONCE_SALT', 'put your unique phrase here');

/**#@-*/

/* Multisite */
define('WP_ALLOW_MULTISITE', true);

/**
* 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', 'da_DK');

/**
* 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');`

@modemlooper,

Its not a BP component, its actually a page under the page post_type.

I’ve now got my code working, it was conflicting with the BP custom profile menu plugin (or vice versa). After disabling that plugin and applying the suggestion as provided by Shane, it now works.

However when using the BP custom profile menu plugin, whatever pages were added (as per the normal WordPress Menu system) would correctly load themselves upon navigating to said URL.

With the manual method I am using above, the URLs do 404 on me.

So using the screen_function callback I can run a query for the page named account – which is fine, happy to do that.

But I’d like to know whether there is a particular method I need to apply (rewrite rule) to have the links work (navigate to their permalink destination) without having to use the screen function?

Anyway, for now thanks for the assistance and to Shane for providing the insight I needed to get this working correctly.

Also, wordpress version: 3.5.1 and buddypress version: 1.6.4

• WordPress 3.5.1
• BuddyPress 1.6.4
• bbPress 2.2.4

After we had converted our legacy forum to bbPress 2, I created a new forum category called “Projects” and made all the remaining group forums parent to that category. By remaining, I mean that the other group forums had now been re-purposed as ordinary forums with no group attached. I did not re-link the remaining group forums with their respective groups until a few months (and probably a BuddyPress and bbPress update in between) after the initial forum conversion.

We have a simple hierarchy. 3 main categories (Troubleshooting, Development and Projects) act as parents for all underlying forums. The ‘Projects’ category holds all old and new group forums. We followed the BP Docs to do the conversion right.

There’s no code field showing up on my registration page. I have used BAW before in combination with S2members, and it worked just fine. I posted about this in the wordpress support forum, but I didn’t get a reply.