MyVideoGameList/myvideogamelist.com
MyVideoGameList/myvideogamelist.com
Watch
3
0
Fork
You've already forked myvideogamelist.com
 0
Code Issues 33 Pull requests 3 Projects 2 Releases Activity Actions

Replace the admin user Banned select with a toggle #1012

New issue
Closed
opened 2026-11-05 11:07:13 -06:00 by Codex · 2 comments
Codex commented 2026-11-05 11:07:13 -06:00
Member
Copy link

The admin user edit form should represent the existing boolean ban state with a direct on/off control.

The change must preserve both banning and unbanning behavior when the form is submitted.

Scope

  • Update the Banned control on the admin user edit Blade page from a select menu to a toggle or checkbox.
  • Keep the current admin authorization, user-edit route, and unrelated account fields unchanged.
  • Ensure the submitted value is normalized so an unchecked toggle explicitly persists the unbanned state.

Acceptance Criteria

  • The admin user edit page renders Banned as a toggle or checkbox and no longer renders a select input for that field.
  • The control is checked when the account is banned and unchecked when it is not banned.
  • Submitting the form with the toggle enabled persists the banned state.
  • Submitting the form with the toggle disabled persists the unbanned state.
  • Existing admin authorization and validation behavior remain intact.

Test Coverage Required

  • Feature coverage verifies the edit page exposes a toggle or checkbox for Banned rather than a select.
  • Feature coverage verifies both enabled and disabled submissions persist the corresponding account state.
  • Existing admin user-edit behavior for authorization and unrelated fields remains covered.

Progress Checklist

  • Locate the Banned field in the admin user edit Blade template.
  • Confirm the existing request/controller persistence path and boolean representation.
  • Implement the toggle and unchecked-value normalization.
  • Add or update focused feature tests for rendering, banning, and unbanning.
The admin user edit form should represent the existing boolean ban state with a direct on/off control. The change must preserve both banning and unbanning behavior when the form is submitted. ## Scope - Update the Banned control on the admin user edit Blade page from a select menu to a toggle or checkbox. - Keep the current admin authorization, user-edit route, and unrelated account fields unchanged. - Ensure the submitted value is normalized so an unchecked toggle explicitly persists the unbanned state. ## Acceptance Criteria - The admin user edit page renders Banned as a toggle or checkbox and no longer renders a select input for that field. - The control is checked when the account is banned and unchecked when it is not banned. - Submitting the form with the toggle enabled persists the banned state. - Submitting the form with the toggle disabled persists the unbanned state. - Existing admin authorization and validation behavior remain intact. ## Test Coverage Required - Feature coverage verifies the edit page exposes a toggle or checkbox for Banned rather than a select. - Feature coverage verifies both enabled and disabled submissions persist the corresponding account state. - Existing admin user-edit behavior for authorization and unrelated fields remains covered. ## Progress Checklist - [x] Locate the Banned field in the admin user edit Blade template. - [x] Confirm the existing request/controller persistence path and boolean representation. - [x] Implement the toggle and unchecked-value normalization. - [x] Add or update focused feature tests for rendering, banning, and unbanning.
Codex changed title from Change Account Banned Select Input Into Toggle to Replace the admin user Banned select with a toggle 2026-11-05 11:07:44 -06:00
Codex self-assigned this 2026-11-06 12:36:07 -06:00
Codex commented 2026-11-06 15:34:08 -06:00
Author
Member
Copy link

Replace the admin user edit form’s Banned select with a styled toggle.

A hidden N value makes unchecked submissions explicitly save the unbanned state, while checked submissions retain the existing Y value. The toggle preserves submitted state after validation errors and uses the existing controller, authorization, and ban behavior.

Verification: 72 feature tests passed (404 assertions), including toggle rendering, banning/unbanning, validation, admin authorization, profile fields, session invalidation, and Fider synchronization. Pint, PHPStan, frontend build, and diff checks passed.

Fixes #1012

Replace the admin user edit form’s Banned select with a styled toggle. A hidden N value makes unchecked submissions explicitly save the unbanned state, while checked submissions retain the existing Y value. The toggle preserves submitted state after validation errors and uses the existing controller, authorization, and ban behavior. Verification: 72 feature tests passed (404 assertions), including toggle rendering, banning/unbanning, validation, admin authorization, profile fields, session invalidation, and Fider synchronization. Pint, PHPStan, frontend build, and diff checks passed. Fixes #1012
Codex commented 2026-11-06 15:37:27 -06:00
Author
Member
Copy link

Merged PR #1020 is deployed to development and production from master revision ce26c706fb. Both release manifests end in +pr1020-ce26c706, and the deployed Blade template SHA-256 matches the merged source. Compiled Blade syntax checks and view-cache rebuilds passed; unrelated application files, assets, and configuration were checksum-guarded. No migrations, dependency changes, or account/domain-data writes were performed.

The toggle submits Y when enabled and an explicit hidden N when disabled. Validation failures retain the submitted state. Existing authorization, validation, ban/session behavior, and unrelated account fields are preserved. Selecting the banned role still forces a ban, so clearing the toggle alone does not override that role; unbanning does not introduce account restoration or external-service reactivation.

Verification before merge: 72 feature tests passed with 404 assertions, plus Pint, PHPStan, the frontend build, and diff checks. Post-deployment HTTPS smoke checks passed for home/login on both sites, and unauthenticated admin edit requests redirect to login. No live accounts were banned or unbanned during deployment verification.

Rollback backups:

  • Development: /home/mvgldev/deploy-backups/pr1020-ce26c706-4a24jgz5
  • Production: /home/mvgl/deploy-backups/pr1020-ce26c706-7muf7x_d

Each deployment account retains ~/deploy-staging/pr1020-ce26c706/deploy.py. Run it as the matching account with ~/bin on PATH and --rollback to restore the prior template/release manifest and rebuild the view cache.

Merged PR #1020 is deployed to development and production from master revision ce26c706fb3decc045975e6b161b10c17fb412f6. Both release manifests end in +pr1020-ce26c706, and the deployed Blade template SHA-256 matches the merged source. Compiled Blade syntax checks and view-cache rebuilds passed; unrelated application files, assets, and configuration were checksum-guarded. No migrations, dependency changes, or account/domain-data writes were performed. The toggle submits Y when enabled and an explicit hidden N when disabled. Validation failures retain the submitted state. Existing authorization, validation, ban/session behavior, and unrelated account fields are preserved. Selecting the banned role still forces a ban, so clearing the toggle alone does not override that role; unbanning does not introduce account restoration or external-service reactivation. Verification before merge: 72 feature tests passed with 404 assertions, plus Pint, PHPStan, the frontend build, and diff checks. Post-deployment HTTPS smoke checks passed for home/login on both sites, and unauthenticated admin edit requests redirect to login. No live accounts were banned or unbanned during deployment verification. Rollback backups: - Development: /home/mvgldev/deploy-backups/pr1020-ce26c706-4a24jgz5 - Production: /home/mvgl/deploy-backups/pr1020-ce26c706-7muf7x_d Each deployment account retains ~/deploy-staging/pr1020-ce26c706/deploy.py. Run it as the matching account with ~/bin on PATH and --rollback <backup-path> to restore the prior template/release manifest and rebuild the view cache.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
codex/issue-1014-verified-gamer-entries
renovate/npm/master/laravel-vite-plugin-3.2.1
renovate/npm/master/concurrently-10.0.7
dev
No results found.
Labels
Clear labels   
automated

   
code-quality

   
component: admin dashboard
The issue is related to the admin dashboard functionality.

  
component: backend
The issue is related to the backend code.

  
component: billing
The issue is related to our billing and payment system functionality.

  
component: content management
The issue is related to site content and moderation functionality.

  
component: faqs
The issue relates to our frequency asked questions and their categories.

  
component: game genres
The issue is related to genres in relation to games.

  
component: game lists
The issue is related to user-facing game list functionality.

  
component: game reviews
The issue relates to the game reviews functionality.

  
component: game search
The issue is related to the user-facing game search functionality.

  
component: games
The issue relates to games in our database.

  
component: internal notifications
The issue is related to the functionality of notifications sent for internal usage.

  
component: platforms
The issue is related to platform functionality.

  
component: security
The issue relates to the security issues within the app.

  
component: tests
The issue relates to unit and feature tests.

  
component: user api
The issue relates to the user-facing API.

  
component: user badges
The issue is related to our badge/achievements functionality.

  
component: user blogs
The issue is related to blogging functionality.

  
component: user consoles
The issue is related to user console lists functionality.

  
component: user favorites
This is issue is related to the favorites functionality.

  
component: user friends
The issue relates to the friending functionality.

  
component: user notifications
The issue is related to user-facing notifications functionality.

  
component: user profiles
The issue is related to user profile functionality.

  
component: user site notifications
The issue relates to the functionality of notifications shown to users directly on the website.

  
component: user wishlists
This issue is related to the wishlists functionality.

  
component: web design
This issue is related to the design of the website.

  
dependencies
Pull requests that update a dependency file.

  
javascript
Pull requests that update Javascript code

  
php
Pull requests that update PHP code.

  
priority
high
 The issue is considered a high priority.

  
priority
low
 This issue is considered a low priority.

  
priority
medium
 This issue is considered a medium priority.

  
security-hotspot

   
source: codex

   
source: sonarqube
  
status
awaiting feedback
 The issue is awaiting feedback from others.

  
status
backlog
 Issues that are in a backlog status.

  
status
done
 The issue has been completed and closed out.

  
status
in progress
 The issue is in progress and being actively worked on.

  
status
in queue
 The issue is in queue and will be worked on shortly.

  
status
in review
 The issue work has been completed and now the work needs to be reviewed.

  
status
needs codex review
 Use this tag to have Codex spiffy up your issue.

  
status
needs investigation
 The issue describes a problem which needs further investigation.

  
status
wontfix
 This issue will not be worked on.

  
type: bug
The issue describes something working the way it wasn't intended too.

  
type: documentation
Improvements or additions to site documentation.

  
type: feature
A new feature for the website.

  
type: improvement
An improvement on an existing feature.

  
type: regression
The issue describes a function that previously worked and no longer does.

  
type: task
A small-ish task.

No labels
automated
code-quality
component: admin dashboard
component: backend
component: billing
component: content management
component: faqs
component: game genres
component: game lists
component: game reviews
component: game search
component: games
component: internal notifications
component: platforms
component: security
component: tests
component: user api
component: user badges
component: user blogs
component: user consoles
component: user favorites
component: user friends
component: user notifications
component: user profiles
component: user site notifications
component: user wishlists
component: web design
dependencies
javascript
php
priority
high
priority
low
priority
medium
security-hotspot
source: codex
source: sonarqube
status
awaiting feedback
status
backlog
status
done
status
in progress
status
in queue
status
in review
status
needs codex review
status
needs investigation
status
wontfix
type: bug
type: documentation
type: feature
type: improvement
type: regression
type: task
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
New Features - Part 1
Assignees
Clear assignees
No assignees
Codex
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MyVideoGameList/myvideogamelist.com#1012
No description provided.