Remove the unavailable Public Profile column from the banned-users admin table #970

New issue

Open

opened 2026-10-15 08:05:03 -05:00 by Codex · 0 comments

Codex commented

2026-10-15 08:05:03 -05:00

Member

The /admin/users/banned page is an admin dashboard view for user-management data.

The issue reports that the Public Profile column always renders Unavailable, so it provides no useful information and should be removed from the table presentation.

The change is limited to the banned-users page and should preserve the remaining user-ban data and actions.

Scope

Update the banned-users admin page view to remove the Public Profile table header and corresponding row cell.
Review the route/controller data passed to the page and remove any profile-specific presentation data only if it is exclusively used by the deleted column.
Add or update focused feature coverage for the banned-users page so the remaining table output is preserved and the removed column does not return.

Acceptance Criteria

/admin/users/banned no longer renders a Public Profile column header.
Banned-user rows no longer render the Unavailable value for that removed column.
All other banned-user columns, pagination, and available admin actions remain unchanged.
The page remains accessible only under its existing admin authorization and route behavior.

Test Coverage Required

Feature coverage requests the banned-users admin page and asserts that the Public Profile header and Unavailable value are absent.
The same coverage asserts that the existing banned-user table content still renders.

Progress Checklist

Locate the banned-users route, page view, and existing feature coverage.
Remove the Public Profile header and row cell from the banned-users table.
Remove now-unused profile presentation data if the page no longer consumes it.
Run the focused banned-users feature test and format changed PHP files.

The `/admin/users/banned` page is an admin dashboard view for user-management data. The issue reports that the Public Profile column always renders `Unavailable`, so it provides no useful information and should be removed from the table presentation. The change is limited to the banned-users page and should preserve the remaining user-ban data and actions. ## Scope - Update the banned-users admin page view to remove the Public Profile table header and corresponding row cell. - Review the route/controller data passed to the page and remove any profile-specific presentation data only if it is exclusively used by the deleted column. - Add or update focused feature coverage for the banned-users page so the remaining table output is preserved and the removed column does not return. ## Acceptance Criteria - `/admin/users/banned` no longer renders a `Public Profile` column header. - Banned-user rows no longer render the `Unavailable` value for that removed column. - All other banned-user columns, pagination, and available admin actions remain unchanged. - The page remains accessible only under its existing admin authorization and route behavior. ## Test Coverage Required - Feature coverage requests the banned-users admin page and asserts that the Public Profile header and `Unavailable` value are absent. - The same coverage asserts that the existing banned-user table content still renders. ## Progress Checklist - [ ] Locate the banned-users route, page view, and existing feature coverage. - [ ] Remove the Public Profile header and row cell from the banned-users table. - [ ] Remove now-unused profile presentation data if the page no longer consumes it. - [ ] Run the focused banned-users feature test and format changed PHP files.

Codex added the

status

needs codex review

label

2026-10-15 08:05:03 -05:00

Codex changed title from ~~Remove Public Profile Column on Banned Users Page~~ to Remove the unavailable Public Profile column from the banned-users admin table

2026-10-15 08:05:35 -05:00

Codex added

component: admin dashboard

component: user profiles

and removed