Settings and Messages

[chrisclayton]

I'd like to propose that we consider moving the settings and messages components out of the members profile component and into their own directory.

Both of them (especially messages) are top-level functionality (like the activity stream) that should be front and center in a social community and not hiding behind a users profile nav. Also unlike other components such as the users activity, profile and groups they have joined those two aren't public-facing and do not represent who the user is and why they are on the site.

[DJPaul]

Settings and Private Messaging are separate components; what I think you're talking about is making a change to a default theme. This is not something we're likely to do to BP-Default for backwards-compatibility reasons with people using the theme and/or child themes. Nothing stopping a custom theme building built for this, of course :)

[chrisclayton]

Sorry, should have wrote it better, what i meant was the URL structure of messages, and allowing users to enable messages to be in the root of the site (like example.org/mail/view/12345)instead of hidden away under their user profile. (currently it's example.com/members/username/messages/view/12345)

possibly something like a define ('BP_ENABLE_ROOT_MESSAGES', true);

Same with settings (example.com/settings instead of /members/username/settings)
Anyways, might leave this closed and write a plugin for it instead.

[boonebgorges]

I've seen this request with clients before.

chrisclayton - I don't think we'd consider moving the whole shebang for everyone, but a flag like the one you suggest is not the worst idea. It will probably involve some funny business in the catch_uri function, where the current_component and other low-level globals get set. If you'd like to work up a patch, and it turns out to be relatively easy, I think we could consider it. (Otherwise, like you suggest, this should be pretty doable with a plugin.)

[chrisclayton]

Deal. reopening (for now) and assigning to myself.
We'll re-discuss the status of this ticket once a patch is done.

[chrisclayton]

I'm closing this and releasing this as a plugin. This is plugin territory, rather than core as I imagine cores implementation is OK for the majority.