Opened 16 years ago
Closed 12 years ago
#1990 closed enhancement (fixed)
Settings enhancement thoughts for 1.3
| Reported by: | johnjamesjacoby | Owned by: | johnjamesjacoby |
|---|---|---|---|
| Priority: | major | Milestone: | 1.5 |
| Component: | Core | Version: | |
| Severity: | normal | Keywords: | |
| Cc: |
Description
For 1.3 I'd like to flesh out bp-settings along with bp-xprofile; they have such similar qualities that doing both side-by-side or at least having two teams tightly in sync with each other, would be a good idea.
I would personally like to see settings be more than just for users. If bp-settings has an API behind it, then anything can tap into it, similar to the way the activity stream does for users and groups. I think that every component (groups, activity, users, blogs, forums) has or could have settings, as well as blogs and even the entire BuddyPress installation.
A BuddyPress specific domain.com/settings/ page (password protected or role based access control) would be a nice way to avoid going into the depths of wp-admin for anything BuddyPress related.
Change History (3)
#2
@
15 years ago
I'm in favor of something like this; we'd also need to make sure current things like the edit avatar screen are properly moved over to this Settings API.
FWIW, I've been hacking together a universal settings template for a theme I'm working on (merging the current settings pages + profile subnav items), however the permalinks are all different ;)
#3
@
12 years ago
- Milestone Future Release → 1.5
- Resolution → fixed
- Severity → normal
- Status new → closed
Our current settings component is exactly this, using BuddyPress existing API's for extending existing components. Closing as fixed and moving into the 1.5 milestone when Settings was properly introduced.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Switching to future release as there is unlikely to be time for this in 1.3, plus we need to review exactly what this ticket is proposing.