Opened 2 years ago

Last modified 19 months ago

#6326 new defect (bug)

Need to synchronize authors' lists on Rosetta sites

Reported by: tobifjellner's profile tobifjellner Owned by:
Milestone: Priority: high
Component: International Sites (Rosetta) Keywords:


Despite having the role Locale Manager, I wasn't able to publish the localized Release post for WordPress 6.0 at
The dropdown for choice of author for the post was just 3-4 usernames long, so I had to publish from the name of "" instead.

As I was trying to figure out what had happened, I decided to remove myself as user on the local site, and then add myself back again. (I was able to do this thanks to my special role as network admin.) And this worked. Now my name got added to the list of possible author names.

So it seems that we in the Rosetta may have sites where a lot of "contributors", "locale managers", and "editors" currently can't be selected as authors.

I don't know how this happened. I don't know if this may be a problem in core or in other parts of wp-org, but at least this needs to be checked and fixed on the Rosetta sites.

Change History (5)

This ticket was mentioned in Slack in #polyglots by nao. View the logs.

2 years ago

#2 @audrasjb
19 months ago

This is still an annoying issue and I can reproduce it on fr_FR.

#3 @dd32
19 months ago

In 12143:

Display the Post Editor dropdown based on who has edit_posts capabilities rather than based on who has what user level or role.

See #6326.

#4 @dd32
19 months ago

In 12144:

Rosetta: Store Locale Manager role capabilities on the role itself, rather than synamically adding them.

This allows for WP_User_Query to find the role, which allows for users with the role to show in the Post Authors dropdown.

See #6326

#5 @dd32
19 months ago

This is related to a WordPress core REST API issue and a Gutenberg issue.

The WordPress REST API includes a /users?who=authors API endpoint that lists users, this fails to take into account custom user roles.

WordPress 5.9 fixed this by adding a ?capabilities=edit_post query method, but Gutenberg still doesn't use it for the dropdown. Not that it would matter, as the capability lookup also doesn't work for the Rosetta custom roles...

See for the upstream issue.

Fixes incoming... well, fixes above :)

Note: See TracTickets for help on using tickets.