BuddyPress.org

Hi there,

What theme are you using and is there a chance that you edited any theme files?

Activation is not visible

Not that I’m aware of, The only other things to check is your theme – try it with 2017, and if you have any customisations that might affect it. switching your theme to 207 will rule our most of these.

@nhorstmann all the values are getting printed as comma separated values

You can add following codes inside child theme function.php and then it will add a span to them base on field type and you can add css for them.

add_filter( 'bp_get_the_profile_field_value',           'xprofile_filter_add_class_profile_data',          9, 3 );
function xprofile_filter_add_class_profile_data( $field_value, $field_type = 'textbox' ) {
	global $field,$bp;

	
	if ( 'datebox' === $field_type ) {
		return $field_value;
	}

	if ( strpos( $field_value, ',' ) === false ) {
		return $field_value;
	}

	if ( strpos( $field_value, ',' ) !== false ) {
		// Comma-separated lists.
		$list_type = 'comma';
		$values    = explode( ',', $field_value );
	}

	if ( ! empty( $values ) ) {
		foreach ( (array) $values as $value ) {
			$value = trim( $value );
		    $new_values[] = '<span class="value-' . $field_type . '">' . $value . '</span>';
		}

		if ( 'comma' === $list_type ) {
			$values = implode( '  ', $new_values );
		} 
	}

	return $values;
}

@vapvarun Thank you, yes, it’s definitely a theme issue, I was leaving the comment so others who found this thread knew where to start in resolving the error.

In regards to Kleo, version 4.3.8 is compatible with BP 3.0.

@bossmanuk try to debug with default WordPress theme (2017) with BuddyPress plugin only it might be possible some theme code is creating an issue.

@aronprins if that’s issue with default theme as well You can submit at https://buddypress.trac.wordpress.org/report

@sjregan then it must be theme specific error, We had also got similar reports for Kleo users. You can consult with their support.
As per my understanding up to now, a theme can not have inbuilt support for both sets of BuddyPress template files, they have to make their choice and define inside theme code for which template set they have added dedicated support.

@otalatita at which url you are getting above error.
You can also confirm from Kleo support if they have updated their theme for nouveau support.

@djpaul I received the same error in a theme that hadn’t been updated to support 3.0. The error did not occur when using the twentyseventeen theme.

Try deactivating all other plugins, also try switching to the 2017 theme to rule out your theme.

@shahriar83 You have already created a thread with BP activity plus support, Explain to them how to replicate the issue.

You can replicate the issue with Template Pack BuddyPress Nouveau after BP 3.0 install using WordPress Default theme “Twenty Seventeen” at singe group activity page.

@geertbaven code might be written inside the template file of the theme
theme-name/buddypress/groups/single/home.php

You will need to remove bp_is_group_forum() code; you are not using forums that’s why it’s creating an issue.
Inside the latest version above code is removed, in core discussion developers had talked about it to put it back.

You can override edit page template inside the child theme
buddypress/bp-templates/bp-legacy/buddypress/members/single/profile/edit.php
at following path
child-theme/buddypress/members/single/profile/edit.php

@djpaul thanks for the feedback. I’d say then that having a dropdown template pack option in the options page gives the impression that we can switch between the 2 as long as a theme supports both. In fact if I start working with BP + Twenty Seventeen or underscores, I need to stick with whichever pack i choose from the beginning if I make modifications to bp templates or have nouveau/legacy specific functions.

concept of multiple small template packs being active at the same time

I wouldn’t need multiple packs active at the same time just for the theme to respond to whichever pack is active. I guess I should have a child theme that works with legacy and another child theme for nouveau… should we be moving away from the legacy pac? if so, my objective of using the same theme for both isn’t needed.

Imagine a BuddyPress Template Pack as something analogous to a WordPress theme. You can’t have a child theme compatible with multiple parent themes.

And you can’t have a template pack compatible with multiple themes. I don’t think there is anything in the template hierarchy – like the named folders that you suggest – that would let you do this. I suppose we could add something but I do not think this would be a good thing for the project at the moment.

We have discussed a concept of multiple small template packs being active at the same time and we might want to support this sort of folder structure then. But not now.

@djpaul but lets say we want the THEME to remain compatible with both? would it be possible to switch between the 2 template packs for a theme having a the override/buddypress folder in order to modify bp templates and still have the theme stay compatible.

I can look for custom functions for each pack when i switch back and forth like so no? so that i can try to make them continue to work for each…

if(class_exists('buddypress')) {
  
  if( bp_get_theme_package_id()  == 'nouveau') { 
  my custom nouveau actions, functions and stuff
  enequeue custom nouveu.css
  } else {
  my custom legacy actions, functions and stuff
  enequeue custom legacy.css
  }

}

How to do this with the theme overrides in the theme/child theme’s /buddypress folder?

should this work?
/bp-nouveau/buddypress/…template overrides
/bp-legacy/buddypress/…template overrides

So in this way my theme can continue working with both packs…

@mechwiy You can add a new class to the body based on role
Added following codes inside child theme functions.php or using snippet plugin

add_filter( 'body_class','adminbar_body_classes' );
function adminbar_body_classes( $classes ) {
 
if ( !current_user_can( 'level_10' ) ) {
				$classes[] = 'no-adminbar';
			}
     
    return $classes;
     
}

after that add following inside custom CSS using customizer

html body.no-adminbar {
    margin-top: -32px !important;
}
body.no-adminbar #wpadminbar {
    display: none;
}

@bassibabes1 on your site register auto login is enabled and that might be a reason users are not getting activation emails. I had registered at your site, and I was logged in at the same time. You might be added any plugin or custom codes inside the theme on purpose.

@shahriar83 seems working fine with Flatsome if you have not customized any template inside child theme
https://drive.google.com/a/wbcomdesigns.com/file/d/1QkXAnrqFYFKV3kLu47QQ0hiBD7TJZIfz/view?usp=drivesdk try to deactivate other bp related plugins to debug the issue.

I am facing the same/or very similar issue.
When I start write something in group activity home post button is still hidden.. but before BuddyPress update the post button always show up when I started write.
Console is clear, no errors with WP_DEBUG true. And my theme developer is not supporting it anymore 🙁

This sounds like it’s possibly a template issue.

To create the activity page, the activity/index.php file is called, this in turn issues the following:

<?php bp_get_template_part( 'activity/post-form' ); ?>

I’m guessing this is what’s failing, as it’s the first template file called, it calls activity/post-form.php which creates the “What’s New” input box. Is that missing from your page?

One of the issues with template files is that they can be loaded from several places depending on the configuration. But in the very least you should check you have one located in:

BP Legacy theme in use - wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress/activity/post-form.php
BP Nouveau theme in use - wp-content/plugins/buddypress/bp-templates/bp-nouveau/buddypress/activity/post-form.php

BuddyPress changed the way it activates users in v3.0.

The activation key should be auto-populated in the Activation Key field if you did not override the template files in your theme.

If you overwrote the template in your theme, you need to alter the activation template file to match the new changes.

See here for a fix:
https://buddypress.org/support/topic/activation-is-not-visible/#post-273341