#16911 closed feature request (worksforme)
Member profile management (WP vs BP)
| Reported by: | youngmicroserf | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Users | Version: | 3.1 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description (last modified by )
One thing that continuously bugs me in WP is the user management/profile fields, particularly with BP added.
A lot has been done in the past releases, but there is apparently still no easy way to quickly customize user profiles and signup forms accordingly beyond the contact methods (without a plugin).
Also, the parallel existence of WP profiles and the BuddyPress X-profiles seems redundant and is confusing, in my opinion. User management/Profiles as such aren't only a feature of a social layer. I believe this should be a core feature, not a plugin-feature...
Change History (9)
#2
follow-ups:
↓ 4
↓ 5
@
15 years ago
- Milestone Awaiting Review
- Resolution → wontfix
- Status new → closed
- Type enhancement → feature request
Yeah, and then you'll want post editing on the front-end and before you know it, there's no backend anymore.
We are not going in that direction.
#4
in reply to: ↑ 2
@
15 years ago
Replying to scribu:
Yeah, and then you'll want post editing on the front-end and before you know it, there's no backend anymore.
I don't think we will loose it that easily ;)
We are not going in that direction.
If we make the backend more MVC like, we *might* be able in the future to offer partial backend functionality in other places more easily: #11517
#5
in reply to: ↑ 2
@
15 years ago
- Summary Frontend user profile editing → Member profile management (WP vs BP)
Replying to scribu:
Yeah, and then you'll want post editing on the front-end and before you know it, there's no backend anymore.
We are not going in that direction.
I'm sorry for bringing up the frontend stuff as an afterthought and distracting from the pain point. My main concern is the profile field part (fields/local avatars etc), particularly, as explained, because of the x-profile redundancy. I think the member aspects are a core issue.
I'll leave the ticket closed but I've renamed it back to the original title because the renaming doesn't reflect my primary intention. I feel that Scribu's closing the ticked was mostly related to the frontend aspect, not the profile/x-profile redundancy aspect. Feel free to leave the ticket closed if you don't think my main concern deserves core attention, but I'd ask you to reopen if your closing the ticket was only a consequence of the frontend aspect mentioned as an afterthought.
Again, I'm sorry for bringing up two (if related) different issues in one ticket.
#6
@
15 years ago
- Description modified (diff)
- Milestone → Future Release
- Resolution wontfix
- Status closed → reopened
So, basically, what you're asking for is a custom fields box, but for users.
That would require a redo of the admin user profile page, which would be a good idea as well.
#8
@
12 years ago
- Resolution → worksforme
- Status reopened → closed
This can be done using existing filters on that page, which many plugins already do. Those filters may not have existed at the time this ticket was created, but many plugins now use them for the purpose outlined in the ticket. An example is edit_user_profile. I guess this is a worksforme
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Related: #2870