WordPress.org

Make WordPress Core

Changes between Initial Version and Version 29 of Ticket #16841


Ignore:
Timestamp:
07/24/2015 12:01:47 PM (4 years ago)
Author:
ocean90
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16841

    • Property Cc marko@… pauldewouters scott@… BandonRandon jonathan@… added
    • Property Component changed from General to Role/Capability
    • Property Summary changed from manually created user roles not showing in author dropdown irregardless of assigned capabilities to Manually created user roles not showing in author dropdown regardless of assigned capabilities
    • Property Milestone changed from Awaiting Review to Future Release
    • Property Keywords needs-patch needs-unit-tests added
  • Ticket #16841 – Description

    initial v29  
    44http://lists.automattic.com/pipermail/wp-testers/2011-March/014130.html
    55
    6 Upon further investigation I have also come across the following:
    7 http://core.trac.wordpress.org/ticket/16451
     6Upon further investigation I have also come across the following: #16451
    87
    98I'm not an expert at debugging this sort of thing, but, I have attempted all within my knowledge thus far, and in looking at all of the returned objects and entries, the only difference I can spot between how the default user roles ( which show up properly in the dropdown ) and the custom created roles ( which do not ) are being returned is that the default user roles, editor for instance, correctly show the deprecated level_7 entry, and the custom user role ( with more assigned privileges than the editor ) does not show user levels in the capabilities array at all, and shows level_0 in the object.