Xprofile Visibility settings not visible on bp-default theme

[sbrajesh]

In BuddyPress 2.0, xprofile visibility settings was moved to settings component as in ticket #5352

It works fine for themes using theme compat but does not work for bp-default or any other theme which contains members/single/settings/profile.php.

The problem is in bp-xprofile-screens.php in the function bp_xprofile_screen_settings() BuddyPress loads plugin template file instead of the members/single/settings/profile.php.

Here is a patch attached to fix the issue.

[boonebgorges]

I haven't got a chance to test this at the moment, but won't this cause problems when bp-default doesn't have the /settings/profile.php template file?

[sbrajesh]

You are right about that. It will only work if the profile.php is present in settings directory of the theme. I updated it like this because BuddyPress had similar changes in BP 1.5 for the settings components and all the themes were forced to be updated.

[r-a-y]

We ran into a similar problem with the Notifications component in v1.9.

I'm torn because the proper "fix" would be to add full support for the "Settings > Profile" tab to bp-default. It wouldn't be too hard to do this, but are we adding new features to bp-default any more?

Since we do add a "Settings > Profile" item in the WP adminbar, it probably does make sense to support bp-default even if this is a new feature.

However, we do need to draw a line in the sand somewhere because we are planning on moving bp-default to the WP Themes directory and any new theme features after v2.0 will definitely not be added to bp-default.

I see two approaches:

1. Add "Settings > Profile" page support to bp-default
2. In the WP adminbar, only show the "Settings > Profile" subnav item for non-bp-default themes (using bp_use_theme_compat_with_current_theme()). This page is not a deal-breaker for bp-default as you can still set the profile visibility from "Profile > Edit".

[r-a-y]

Attached patch only adds the "Settings > Profile" subnav item if the theme isn't bp-default

[boonebgorges]

I'm a bit confused here. At first I thought that this was the same thing as notifications in 1.9. But looking back at the changelog, it appears that bp-default was in fact updated to have the proper templates. See r7960.

The underlying problem in 2.0 is that the bp_core_load_template() call in bp_xprofile_screen_settings() is incorrect. See 5549.03.patch.

As an aside: In the future, we should come to a better consensus about what does and what does not get added to bp-default. If we're going to deprecate, we should actually deprecate. There would've been a way to write this new feature so that it degraded gracefully in bp-default (sorta like 5549.02.patch, but maybe with a more targeted locate_template() check, so that theme authors could manually add support to old themes if they wish).

[r-a-y]

I'm a bit confused here. At first I thought that this was the same thing as notifications in 1.9. But looking back at the changelog, it appears that bp-default was in fact updated to have the proper templates. See r7960.

You're right. Sorry for confusing you! :)

sbrajesh's first patch is identical to yours. Let's commit it.

In the future, we should come to a better consensus about what does and what does not get added to bp-default.

For sure.

[boonebgorges]

sbrajesh's first patch is identical to yours.

D'oh. :)

[boonebgorges]

In 8291:

Correct path to settings/profile template

The new Profile subtab of Settings is broken in bp-default-style themes without
this proper template path.

Fixes #5549

Props sbrajesh

[boonebgorges]

In 8292:

Correct path to settings/profile template

The new Profile subtab of Settings is broken in bp-default-style themes without
this proper template path.

Fixes #5549

Props sbrajesh