Opened 8 months ago
Last modified 7 months ago
#7433 new enhancement
Consider removing logged in block when viewing support forums.
Reported by: | dufresnesteven | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Support Forums | Keywords: | |
Cc: |
Description
I'm not sure why we need to include a block in the support forum that lets me know I'm logged in and helps me log out.
The top admin bar has the same functionality.
Do we need it?
Attachments (2)
Change History (6)
This ticket was mentioned in Slack in #forums by dufresnesteven. View the logs.
8 months ago
@
8 months ago
The global dropdown does include forum related navigation items. Ie. Topics Started. The actual profile page doesn't provide much value for my account at least. Just a few stats. I wonder how others are using the Support profile landing page. We could also maybe add a "Forum profile" as the first link in that dropdown navigational block.
#3
@
7 months ago
I'd prefer a cleaner interface; the forum sidebar block and the function of the global dropdown seem to be similar here.
Also, if a user logs out, this block doesn't offer a login function, which seems a bit inconsistent.
I think we could just add a "Forum Profile" as @dufresnesteven suggested. And if we add the "Forum Profile", I also feel that we can further remove items like "Topics Started", and "Replies Created", etc from the global dropdown, as they can be linked directly from the forum profile page.
Additionally, since this is a global instance for WordPress.org, maybe we could add a "WP.ORG Profile" alongside the Forum Profile as well.
Your display name here is also your link to your profile, which is where they primarily differ in features.
The admin bar is a global instance for WordPress.org, and will take you to your
profiles.wordpress.org
page, while the "contained" sidebar entry is forum-specific, and takes you to your forum profile (which is also used for certain settings that you can not control from the global profile).I'm not sure if we can remove it for this reason, as we need users to have access to both profile sets.