kate522andClaude Opus 5
35bb96e82f
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>
36 lines
1.4 KiB
JavaScript
36 lines
1.4 KiB
JavaScript
'use strict';
|
|
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('node:fs');
|
|
const path = require('node:path');
|
|
const test = require('node:test');
|
|
|
|
const root = path.resolve(__dirname, '..', '..');
|
|
const read = (file) => fs.readFileSync(path.join(root, file), 'utf8');
|
|
|
|
test('submit.css raises the TinyMCE fullscreen container above the fixed navbar', () => {
|
|
const css = read('assets/css/frontend/pages/submit.css');
|
|
|
|
// TinyMCE's skin injects .mce-fullscreen { z-index: 100 } at editor init,
|
|
// after core editor.css, so the fullscreen editor loses to the fixed navbar
|
|
// (.nav-fixed .header, z-index 999). The element+class selector outranks the
|
|
// skin regardless of injection order and restores core's intended 100010,
|
|
// which stays below the submit media dialog (100080).
|
|
assert.match(css, /div\.mce-fullscreen \{\s*\n z-index: 100010;\s*\n\}/);
|
|
});
|
|
|
|
test('the Zibll toolbar affix rules stay removed', () => {
|
|
const css = read('assets/css/frontend/pages/submit.css');
|
|
const jsRoot = path.join(root, 'assets/js');
|
|
const js = fs
|
|
.readdirSync(jsRoot, { withFileTypes: true })
|
|
.filter((entry) => entry.isFile())
|
|
.map((entry) => read(`assets/js/${entry.name}`))
|
|
.join('\n');
|
|
|
|
// No Jio script adds .affix to .mce-top-part (that was Zibll's
|
|
// editextend.js), so the affix positioning rules must not come back.
|
|
assert.doesNotMatch(css, /mce-top-part\.affix/);
|
|
assert.doesNotMatch(js, /mce-top-part/);
|
|
});
|