Files
浅念 601451f22b upgrade: adopt V8.21.3 (V8.13→8.21.3: P5 SFTP/S3, P6 multilingual, editor overhaul, enterprise hardening)
Overlay ~150 upstream items onto our V8.12 base, preserving trade-pro
theme, registry tests, and design docs. Re-applied our patch set
(discovery/env_for/blocks.css/type-mapping/theme_color/frontend entries,
test_theme_pro_v3 mods) — all anchors survived upstream evolution.

New platform enhancement (fixes upgrade-introduced regression):
multilingual.site_locale now honors settings_json.locale, plus
PUT /api/i18n/sites/{id}/locale — standalone English sites get
<html lang='en'> under the V8.15 locale-rewrite pipeline.

compose: adopt V8.21.3 (image 8.21.3-dev.1, /api/ready probes, MySQL/S3
env) with project name pinned to siteforge-v8-10 (data volumes).

Tests: 356 passed / 11 failed — all 11 confirmed pre-existing in
pristine V8.21.3 on this host (10 upstream Windows env + our build test
now green after locale fix). Patch registry updated in plan doc.

Co-Authored-By: Claude Code <noreply@anthropic.com>
2026-10-23 12:31:03 +08:00

895 B

P6 快速操作

登录 http://localhost:8787/ → 我的站点 → 建立中文与英文两个独立 HTTPS 站。

  1. 进入“多语言管理”,创建语言组与两个语言站成员。
  2. 在中文站与英文站分别录入已翻译页面,各自设置 status=published。
  3. 建立翻译内容组(例如 product:example),将两个实际页面 ID 分别关联为 approved。
  4. 重新构建两个站点,并查看生成 HTML 与 Sitemap;无对应翻译的页面不会显示语言互链。
  5. 待翻译文案先存为 draft,可以关联为 pending,待审核确认以后改为 published 并设为 approved。
  6. 使用“构建与交付”审批发布。上线前仍需在真实域名上逐一核对 canonical、链接、翻译质量和 SEO。

数据库升级为加法建表,不会自动复制或修改原网站内容。升级前请先备份现有卷。