-
Notifications
You must be signed in to change notification settings - Fork 0
WP role mapping (built-in + custom) #199
Copy link
Copy link
Closed
Labels
area:authAuthentication & authorizationAuthentication & authorizationarea:migrationWordPress importer + compatWordPress importer + compatphase:P5-migrationPhase 5 — MigrationPhase 5 — Migrationpriority:P1Important — should land in phaseImportant — should land in phaseskill:goGo programmingGo programmingtype:featNew feature or implementation taskNew feature or implementation task
Milestone
Metadata
Metadata
Assignees
Labels
area:authAuthentication & authorizationAuthentication & authorizationarea:migrationWordPress importer + compatWordPress importer + compatphase:P5-migrationPhase 5 — MigrationPhase 5 — Migrationpriority:P1Important — should land in phaseImportant — should land in phaseskill:goGo programmingGo programmingtype:featNew feature or implementation taskNew feature or implementation task
Type
Fields
Give feedbackNo fields configured for issues without a type.
Summary
Map WP roles to gonext roles per doc 08 §7.3. Built-in WP roles map 1:1 to our canonical slugs (
administrator,editor,author,contributor,subscriber; multisite super-admin →super_adminreserved). Custom WP roles are best-effort: diff the capability set against our built-in roles and pick the closest match + a warning. Exact custom-role replication is v2.Design reference
Acceptance criteria
wp_options.wp_user_roles(deserialized PHP)administratorslug (notadmin); includesuper_adminreserved slot (matches doc 06 §6.1 seed)custom_role_best_matchwarningmigration_warningsincludes the original capabilities for v2 exact replicationDependencies
#users-phpass
Complexity
M