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>
This commit is contained in:
kate522andClaude Opus 5 committed
1 parent
5b16bc6e15
commit
35bb96e82f
997 files changed
+28216
-28188
No files matched your search
@@ -1,4 +1,4 @@
|
||||
# AKSRT WordPress Theme
|
||||
# Jio WordPress Theme
|
||||
|
||||
> **版本**: 3.4.0-dev | **架构**: 原生 PHP + WordPress (非 headless)
|
||||
> **要求**: WordPress >= 6.4 | PHP >= 8.1
|
||||
@@ -7,7 +7,7 @@
|
||||
|
||||
## 项目概述
|
||||
|
||||
AKSRT 是一款现代化的 WordPress 主题，采用**原生 WordPress 主题架构**开发（PHP + HTML + CSS + JavaScript），不依赖 REST API 进行前端渲染。
|
||||
Jio 是一款现代化的 WordPress 主题，采用**原生 WordPress 主题架构**开发（PHP + HTML + CSS + JavaScript），不依赖 REST API 进行前端渲染。
|
||||
|
||||
### 核心特性
|
||||
|
||||
@@ -22,14 +22,14 @@ AKSRT 是一款现代化的 WordPress 主题，采用**原生 WordPress 主题
|
||||
## 文件结构
|
||||
|
||||
```
|
||||
AKSRT-theme/
|
||||
Jio-theme/
|
||||
├── functions.php # 入口：常量 + Composer autoload + bootstrap + 单例 init
|
||||
├── style.css # WordPress 主题声明头
|
||||
├── composer.json # 第三方依赖 + 主题 PSR-4（AKSRT\ → src/）
|
||||
├── composer.json # 第三方依赖 + 主题 PSR-4（Jio\ → src/）
|
||||
│
|
||||
├── *.php # WP 核心模板保留根目录
|
||||
│
|
||||
├── src/ # Composer PSR-4 类型根（namespace AKSRT\）
|
||||
├── src/ # Composer PSR-4 类型根（namespace Jio\）
|
||||
│ ├── Admin/ # SPA 编排 + 域控制器 + Schema + Native ops
|
||||
│ ├── Auth/ # 登录 / OAuth / 审核 / 邮箱
|
||||
│ ├── Content/ # 下载 token / 付费内容 / VIP / 可见性
|
||||
@@ -89,7 +89,7 @@ AKSRT-theme/
|
||||
|
||||
## 安装方式
|
||||
|
||||
主题类型（`AKSRT\…`）通过 Composer PSR-4 从 `src/` 自动加载；`vendor/` 不进 Git。**部署或更新主题后必须在主题根目录生成 autoload**，否则会出现 `Class "AKSRT\Core\DomainModel" not found` 等致命错误。
|
||||
主题类型（`Jio\…`）通过 Composer PSR-4 从 `src/` 自动加载；`vendor/` 不进 Git。**部署或更新主题后必须在主题根目录生成 autoload**，否则会出现 `Class "Jio\Core\DomainModel" not found` 等致命错误。
|
||||
|
||||
### 前置：Composer（必做）
|
||||
|
||||
@@ -106,16 +106,16 @@ composer dump-autoload -o
|
||||
确认：
|
||||
|
||||
```bash
|
||||
php -r "require 'vendor/autoload.php'; echo class_exists('AKSRT\\\\Core\\\\DomainModel') ? \"ok\\n\" : \"missing\\n\";"
|
||||
php -r "require 'vendor/autoload.php'; echo class_exists('Jio\\\\Core\\\\DomainModel') ? \"ok\\n\" : \"missing\\n\";"
|
||||
```
|
||||
|
||||
应输出 `ok`。若 PHP 开启了 OPcache，重载 php-fpm / 重启 PHP 后再访问站点。
|
||||
|
||||
### 方式一：直接上传（推荐）
|
||||
|
||||
1. 将整个 `AKSRT-theme` 文件夹上传到 `wp-content/themes/`
|
||||
1. 将整个 `Jio-theme` 文件夹上传到 `wp-content/themes/`
|
||||
2. 在服务器主题目录执行上一节的 `composer install`（若打包时已带上完整 `vendor/` 且已 `dump-autoload`，可跳过）
|
||||
3. WordPress 后台 → **外观** → **主题** → 找到 **AKSRT** → **激活**
|
||||
3. WordPress 后台 → **外观** → **主题** → 找到 **Jio** → **激活**
|
||||
|
||||
### 方式二：ZIP 打包上传
|
||||
|
||||
@@ -126,7 +126,7 @@ php -r "require 'vendor/autoload.php'; echo class_exists('AKSRT\\\\Core\\\\Domai
|
||||
SSH 进入主题目录后：
|
||||
|
||||
```bash
|
||||
cd /path/to/wp-content/themes/AKsrt-theme # 以实际路径为准
|
||||
cd /path/to/wp-content/themes/Jio-theme # 以实际路径为准
|
||||
composer install --no-dev --optimize-autoloader
|
||||
# 或仅刷新映射：composer dump-autoload -o
|
||||
# 可选：reload php-fpm / 清 OPcache
|
||||
@@ -150,9 +150,9 @@ composer install --no-dev --optimize-autoloader
|
||||
|
||||
### 2. 后台配置路径
|
||||
|
||||
WordPress 后台左侧 **Admin Bar** → ⚡ **AKSRT 主题设置**
|
||||
WordPress 后台左侧 **Admin Bar** → ⚡ **Jio 主题设置**
|
||||
|
||||
或直接访问：`/wp-admin/admin.php?page=aksrt-settings`
|
||||
或直接访问：`/wp-admin/admin.php?page=jio-settings`
|
||||
|
||||
### 3. 当前后台域
|
||||
|
||||
@@ -173,7 +173,7 @@ WordPress 后台左侧 **Admin Bar** → ⚡ **AKSRT 主题设置**
|
||||
### 5. 部署注意事项
|
||||
|
||||
- **佣金结算时效**：结算依赖小时级 wp-cron，并有收益页访问触发的懒结算兜底。高流量站点建议禁用 `WP_CRON_LOCK` 场景下的默认 WP-Cron，改用系统 crontab 定时请求 `wp-cron.php`，保证结算与过期任务准时执行。
|
||||
- **反代 / CDN 与 IP 风控**：主题默认按 Cloudflare → 通用代理头顺序识别真实 IP。若需收紧伪造风险，添加 `add_filter('aksrt_trusted_proxies', fn() => ['10.0.0.0/8', '173.245.48.0/20'])`（填入你的代理/CDN 网段）；名单非空时仅当 `REMOTE_ADDR` 命中名单才采纳转发头，否则直接使用 `REMOTE_ADDR`（推广奖励的 IP 日上限、验证码等均依赖该函数）。
|
||||
- **反代 / CDN 与 IP 风控**：主题默认按 Cloudflare → 通用代理头顺序识别真实 IP。若需收紧伪造风险，添加 `add_filter('jio_trusted_proxies', fn() => ['10.0.0.0/8', '173.245.48.0/20'])`（填入你的代理/CDN 网段）；名单非空时仅当 `REMOTE_ADDR` 命中名单才采纳转发头，否则直接使用 `REMOTE_ADDR`（推广奖励的 IP 日上限、验证码等均依赖该函数）。
|
||||
|
||||
---
|
||||
|
||||
@@ -181,20 +181,20 @@ WordPress 后台左侧 **Admin Bar** → ⚡ **AKSRT 主题设置**
|
||||
|
||||
### Settings Facade 分层
|
||||
|
||||
- `AKSRT_Settings` 仍是主题设置的**唯一静态 facade**，外部调用方式保持 `AKSRT_Settings::*`
|
||||
- `JIO_Settings` 仍是主题设置的**唯一静态 facade**，外部调用方式保持 `JIO_Settings::*`
|
||||
- 具体运行时 getter 已按领域拆分到 `inc/classes/settings/`，例如：
|
||||
- `class-aksrt-settings-theme-search.php`
|
||||
- `class-aksrt-settings-post-display.php`
|
||||
- `class-aksrt-settings-home-cms.php`
|
||||
- `class-aksrt-settings-user-runtime.php`
|
||||
- `class-aksrt-settings-integration.php`
|
||||
- `class-aksrt-settings-display-runtime.php`
|
||||
- `class-aksrt-settings-extension-runtime.php`
|
||||
- `class-aksrt-settings-credits-runtime.php`
|
||||
- `class-aksrt-settings-category-runtime.php`
|
||||
- `class-aksrt-settings-capabilities.php`
|
||||
- `inc/bootstrap.php` 会先加载 `settings/class-aksrt-settings.php`，再按领域加载这些 delegate 类
|
||||
- 新增设置运行时逻辑时，优先放入对应 settings 子类；仅把聚合输出、统一入口和跨域装配保留在 `AKSRT_Settings`
|
||||
- `class-jio-settings-theme-search.php`
|
||||
- `class-jio-settings-post-display.php`
|
||||
- `class-jio-settings-home-cms.php`
|
||||
- `class-jio-settings-user-runtime.php`
|
||||
- `class-jio-settings-integration.php`
|
||||
- `class-jio-settings-display-runtime.php`
|
||||
- `class-jio-settings-extension-runtime.php`
|
||||
- `class-jio-settings-credits-runtime.php`
|
||||
- `class-jio-settings-category-runtime.php`
|
||||
- `class-jio-settings-capabilities.php`
|
||||
- `inc/bootstrap.php` 会先加载 `settings/class-jio-settings.php`，再按领域加载这些 delegate 类
|
||||
- 新增设置运行时逻辑时，优先放入对应 settings 子类；仅把聚合输出、统一入口和跨域装配保留在 `JIO_Settings`
|
||||
|
||||
### 添加新辅助函数
|
||||
|
||||
@@ -202,14 +202,14 @@ WordPress 后台左侧 **Admin Bar** → ⚡ **AKSRT 主题设置**
|
||||
|
||||
### 添加新页面模板
|
||||
|
||||
将 `page-{name}.php` 放入 `templates/pages/`，并在 `class-aksrt-templates.php` 中注册。
|
||||
将 `page-{name}.php` 放入 `templates/pages/`，并在 `class-jio-templates.php` 中注册。
|
||||
|
||||
### CSS 组织规范
|
||||
|
||||
| 目录 | 用途 | 加载场景 |
|
||||
|------|------|---------|
|
||||
| `css/frontend/` | 前端公共样式 | 所有前台页面 |
|
||||
| `css/admin/` | 后台管理样式 | 仅 AKSRT 设置页面 |
|
||||
| `css/admin/` | 后台管理样式 | 仅 Jio 设置页面 |
|
||||
| `css/shared/` | 共用组件样式 | 前后端按需加载（如验证码） |
|
||||
|
||||
---
|
||||
|
||||
Reference in new issue
Block a user