  kate522andClaude Opus 5
|
35bb96e82f
|
refactor: rename the theme brand and every identifier from AKSRT to Jio
Full-project rename. `git grep -i aksrt` is now empty apart from the
DBMigrator 3.3.0 changelog note that documents the rename itself.
Code identifiers
- PHP namespace AKSRT\ -> Jio\ (composer PSR-4 + 378 declarations)
- global constants AKSRT_* -> JIO_* (VERSION/DIR/URI, PAY_TYPE_*, CAPTCHA_*)
- procedural functions, hooks, options, meta keys, table names,
cookies, query vars, ajax actions and nonces: aksrt_ -> jio_
- text domain aksrt -> jio; Theme Name -> Jio
- JS globals: aksrtData/aksrtAdminData/... -> jioData/jioAdminData/...,
window.AKSRTCaptcha & friends -> window.JioCaptcha, Aksrt* -> Jio*
- Vue components Aks*.vue -> Jio*.vue (15 files renamed + imports)
- CSS classes/data-attrs/custom properties: aksrt- -> jio-
- REST namespace aksrt/v1 -> jio/v1 (incl. payment gateway callbacks)
Storage layer
- DB tables {prefix}aksrt_* -> {prefix}jio_*; SCHEMA_VERSION 3.2.0 -> 3.3.0
so dbDelta creates the new names on install
- widget id_base aksrt_widget_* -> jio_widget_*
- uninstall.php drop list rebuilt from the actual migrator tables
(dropped 3 stale entries, added the 17 missing ones)
Removed
- hardcoded https://api.aksrt.com/version.json default update endpoint;
get_endpoint() now reads the 「更新端点」 setting and do_check() no-ops
when it is empty
Files renamed: inc/helpers/aksrt-*.php -> jio-*.php (54),
assets/admin/src/components/form/Aks*.vue -> Jio*.vue (15).
Build artifacts regenerated: assets/css/build, assets/js/runtime,
assets/admin/build.
Verified: audit-psr4-paths errors=0, audit-admin-contracts errors=0
(warnings=56, unchanged baseline), 813/813 widget-system tests,
44/44 phpunit, php -l clean across all PHP.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
2026-11-01 20:05:04 +08:00 |
|
|
kate522
|
a4af024f32
|
feat(ban): align ban prompts with the reference theme modals and block page
对照参考主题(Zibll)修正四项偏差，申诉链路从页面整体迁移至弹窗：
- feat(ban): 新增三个 1:1 复刻弹窗（REST /user-ban/{info,appeal,log}-modal）：
查看禁封状态（多彩头 c-gray + 信息行 + 申诉按钮）、禁封申诉（edit-header
gavel/c-blue + 信息框 + 资料项 data[key] 输入 + 审核中态 + 禁止申诉态）、
禁封记录（多彩头 c-yellow + 计数 + 逐条卡片）；user-ban.js 增加
data-aksrt-ban-info/appeal/log 委托与 admin-ajax 申诉提交
- feat(ban): 禁封/解封弹窗的「当前用户已有N次禁封记录」静态文案改为可点击
黄链（N>1），打开禁封记录弹窗；解封视图信息行改复用统一数据源
- refactor(ban): 治理展示态收敛至 Restriction::state_badges()（封号=c-red
违规已封号 / 小黑屋=c-yellow 小黑屋禁封中 / 禁言=c-gray 禁言中，颜色与
字段统一管理）+ get_ban_info()（状态/起止时间/原因/说明/申诉权限，
三弹窗与禁封页共用）
- feat(ban): 登录行为对齐参考主题——移除登录期拦截（enforce_login_ban）
与 complete_login 禁封闸门，封号用户可正常登录；新增 template_redirect
前台禁封页（1:1 zib_user_ban_restrict_login/zib_die_page：红盒提示 +
信息行 + 申诉权限 + 退出登录/申诉按钮，模板 templates/parts/user/ban-block.php）
- feat(profile): 公开主页禁封状态从资料卡下方提示框改为占据身份行元信息位
的 badg 徽章（参考主题 author_header_identity 语义）；用户中心元信息改为
but 按钮（徽章+箭头）打开查看禁封状态弹窗；评论拒绝态链接同源
- refactor: 移除申诉页面模板（page-ban-appeal.php）及其资产/注册/入队、
get_profile_notice/profile_notice 链、state_labels/state_notices/
login_ban_message、UserRuntime 的 public_notice/ban_notice_text 死配置、
report_settings 死键、无消费方的 aksrt_ban_appeal_status 端点
- feat(ban): BanAppeal::ajax_submit 兼容弹窗 data[key] 表单结构
（逐项清洗入库，申诉说明取 data['申诉说明']，旧平铺字段保持兼容）
- chore: 重新构建 public.css/public.min.css（三个新弹窗几何与头部样式）
- test: 契约测试重写（徽章元信息位、三弹窗与记录链接、禁封页、允许登录 +
前台拦截、死代码移除断言），全量 362 项通过
|
2026-09-22 19:14:02 +08:00 |
|