[wp-meta] [Making WordPress.org] #7960: Rosetta Sites and WordPress.org Sub-sites: Access Behavior of /wp-admin/about.php
Making WordPress.org
noreply at wordpress.org
Tue Apr 22 09:36:56 UTC 2025
#7960: Rosetta Sites and WordPress.org Sub-sites: Access Behavior of /wp-
admin/about.php
----------------------------+---------------------
Reporter: kimjiwoon | Owner: (none)
Type: defect (bug) | Status: new
Priority: low | Milestone:
Component: Support Forums | Resolution:
Keywords: |
----------------------------+---------------------
Comment (by kimjiwoon):
Replying to [comment:1 dd32]:
Thanks @dd32 — I tested again and can confirm that the redirect now works
as expected.
- Visiting https://ko.wordpress.org/support/wp-admin/about.php redirects
to my profile page, so it seems the core issue is resolved ✅
- On https://ko.wordpress.org/wp-admin/about.php I still have access, but
that's because I have backend permission (as part of the locale site
team), so I don't think this is a bug.
That said, if the page is going to remain accessible anyway, I think it
would be reasonable to include a UI element for it on
https://ko.wordpress.org/wp-admin/index.php.
- I've confirmed that the site is running version 6.9-alpha-60178.
From a UX perspective, I’d just like to share one additional thought:
Since accessing URLs like this isn’t a typical user behavior, it’s usually
learners like myself — trying to understand the meta structure of
WordPress.org — who explore these pages.
This kind of redirection might feel unintuitive to users who are trying to
understand the internal multisite structure of WordPress.org — especially
contributors or learners analyzing the platform behavior.
For example, WordPress.com provides more explicit responses like:
1. “You don’t have permission to access this page.”
2. HTTP 403 Error
3. A helpful message like:
_"You are logged in as 'username' and do not have the necessary
privileges to access this dashboard."_
These kinds of messages help clarify that the site is running a multisite
setup, and that user roles are intentionally limited.
Just wanted to offer this small UX feedback from the perspective of
someone researching how WordPress.org is architected. 🙂
Thanks again for your quick update and support!
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/7960#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list