[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
Wed Apr 23 02:44:04 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:  closed
 Priority:  low             |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 > 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.

 This is a reasonable point to raise, but WordPress.org has many
 customizations due to the number of logged in users we have, and the
 general lack of need for wp-admin access for most users (and all
 visitors).

 This is more of a user experience "improvement" even though it's less
 clear as to why you're being redirected. The experience for the majority
 of users landing on a WordPress.org page that says "you can't access this"
 and not knowing what they're accessing has more problems.

 You're one of the few users with wp-admin access, and as such you're going
 to see more wp-admin urls than most, but most users should '''never''' see
 a link to wp-admin anywhere on WordPress.org.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7960#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list