Журнал изменений

update.php carries news, pages, faq, help, links, files and content of a site that ran the 6.3 update into Node types with their categories, comments, favorites, rating balances, resources and files. The new table _node_legacy maps every old address to its material, so the old links of the outside world follow the content. The views and cards of Node regain the dials, chips and marks the old modules rendered.

Core changes:

1. The migration script (update.php, lang/*.php):

• Main administrator only; a preview, then a POST with a token scoped update; the stages stash, types, data, files and activation run from a manifest in storage/backup/update/node and resume after a stop
  • pages becomes the type docs with comments and rating, content a type without extension
  • texts move from the trusted HTML the old modules rendered into BB and Markdown; unknown blocks stay in [usehtml]; code blocks lose only editor line breaks
  • [attach] files go to the root of the type under managed names; directly linked files are copied to uploads/archive/<module>/ and their links rewritten
  • help tickets are published materials whose open or closed state lives in _node_support; replies become comments
  • orphaned comments and favorites keep their rows under old<module>; admin rights move to node-<type>
• The counter of _nodes continues above every old id, so an old address never names a new material
• Seven _NODE_MIG* constants in all six locales

2. Old addresses (setup/sql/*.sql, core/classes/node/query.php, core/system.php, index.php, modules/node/index.php):

• Table _node_legacy (modul, oid, nid), foreign key to _nodes with cascade, in table.sql and the 6.3 update
• NodeQuery::getNodeLegacy() and getNodeLegacyUrl() answer 301 on the way to a 404: a missing material of a type, an unknown op of a type, and a name that is no longer a module (pages goes to docs)

3. Writer rules (core/classes/node/service.php):

• A new type of one of the nine replaced names takes over the upload rule its old module left in config/uploads.php instead of being refused as a taken name
• A migrated material earns no second publication award when a moderator publishes it, now or by schedule

4. The look of the old modules (modules/node/index.php, modules/node/admin/, core/system.php, templates/lite//node/*):

• getNodeMetaVars() gives views and cards the comment chip, the fresh mark, the category icon, favorite, rating and the moderator dial; the view adds share, the author menu and the #id anchor
• getNodeModerDial() and getNodeMoveLabel() move to the core: the site dial and the panel list are one function, and the _NODE_TO* constants move to lang/*.php
• The category map carries the icon; the download chip counts links as well

5. Tests (tests/Unit/Node*Test.php, tests/Support/node_probe.php, tests/Support/contract_probe.php, tests/Unit/CommentIsolationTest.php):

• _node_legacy lists, constraints, indexes and cascade; getNodeLegacy(); the reward rule; the adopted upload rule
• The comment parity samples leave Node types out, whose read rights the legacy queries never knew
• update.php is exempt from the comment isolation scan: it reads the old tables by design

Benefits:

• One run moves a site off the removed modules without losing a comment, a vote or a link
• Crawlers and old bookmarks reach the moved content instead of a 404

Technical notes:

• New table _node_legacy; the old module tables are only read and stay in place
• docs/NODE.md documents the migration, the table, the 301 rules and the template keys

The confirmation an admin screen shows after a save was compared in eight faces before one went into the theme. The series stays on the stand beside the others, so the choice can be seen against what it was chosen from.

Core changes:

1. The series (demo/flash-01-stamp.html ... demo/flash-08-orbit.html):

• One stage in all eight: the head of the blocks module, the flash where module-head.html prints it, the info alert of the live page under it, a desk that replays the flash, and the four tones side by side
• Each face changes the arrival, the countdown, the exit and the success tick, and nothing else
• The faces stand on the bar the theme had before the ring, which their shared styles restore

2. Stand behaviours (demo/assets/demo.js, demo/assets/demo.css):

• DEMO_FLASH manifest and its place in DEMO_SERIES, so the gallery shows the series by itself
• data-demo-flash replays a template into data-demo-flash-host and lets the theme's htmx:afterSwap hook arm the autohide; data-demo-flash-loop plays it again after the exit
• data-demo-about fills the card of a face from its manifest entry

3. Reference (demo/README.md):

• The sixth series, its table of faces, and the note that 03 Ring lives in the admin theme

Benefits:

• The countdown and the exit on the stand are those of slaed.js, not an imitation

Technical notes:

• The stand does not ship; nothing outside demo/ changes

The flash an admin screen prints after an action was an info alert that counted down with two hair lines, and the success tick and the accent megaphone pulsed exactly as the info letter did. A confirmation is now a success alert, the flash springs in and counts down on a ring round its tick, and the success and accent glyphs have motion of their own in both themes.

Core changes:

1. The flash is a success (core/system.php, core/helpers.php):

• getFlashHtml() passes type success, or warn for a refusal, instead of is_warn
• The saved-help notice of a module passes type success as well

2. The ring countdown (templates/admin/fragments/alert.html, templates/admin/assets/css/theme.css):

• sl-alert-flash-bar holds an SVG circle with pathLength 100; stroke-dashoffset runs it out over --sl-flash-dur
  • the ring is centred on the tick, its track an inset shadow of --sl-flash-mix of the tone
• The flash springs in with sl-alert-pop and leaves scaled down; the two hair lines and sl-alert-flash-frame are gone

3. Tone glyphs (templates/admin and templates/lite, assets/css/theme.css):

• Success: sl-alert-land, a turn in, then sl-alert-glow
• Accent: the megaphone tips up from its grip (sl-alert-announce) and two arcs of voice leave its bell (sl-alert-voice)
• Info keeps its pulse, warn its shake, error its beat

4. Tokens and contract (base.css of both themes, tools/ui-contract.php):

• --sl-alert-ease in both themes, --sl-flash-ring and --sl-flash-mix in admin
• The divergence reasons of .sl-alert-flash and .sl-alert-flash-bar describe the ring

Benefits:

• A confirmation reads as a success at a glance, and no two tones share a motion
• The countdown uses no registered property, so it animates the same in every browser

Technical notes:

• The fragment markup of a flash gains one SVG; the autohide of slaed.js is unchanged
• Motion stands under prefers-reduced-motion; the reduce rules also stop the arc and the ring
• This commit also restores four lines of the previous one that its hunk-wise staging put a few lines off, among them the text colour of a toolbar item in hand

Release 8.0 no longer ships these six modules. Removing their directories alone would have left the core answering for them: a cart route, a shop scope in three shared subsystems, a points action, an extra-field area, feeds, sitemap and search sources, admin counters and eight tables in the installation schema. All of it goes, and the 6.3 update leaves the tables of these modules on an old site untouched.

Core changes:

1. Removed files:

• modules/{auto_links,clients,money,order,shop,whois}, blocks/auto_links.php, their config files and uploads/{auto_links,clients,shop}
• templates/lite/fragments/shop-invoice.html, templates/lite/partials/money-calc-scripts.html

2. Core hooks (core/system.php, core/user.php, core/admin.php, core/helpers.php, index.php, core/security.php):

• The cart helpers and the go=2 route; the shop feed, sitemap section, letter index, rating map and alphabet query; the newsletter audiences of the three client lists; the admin counters of new clients, partners and whois requests; the cabinet links to clients and partners; shop favorites
• getCategoryCounts(), which counted shop products only, and catmids(), whose last caller was the shop branch of Comment; getMailAudience() reads accounts only
• The module and icon names of the removed modules; the editor stores of their columns
• The referer log no longer links a visitor to an auto_links entry and writes no lid

3. Shared subsystems (core/classes/comment.php, rating.php, point.php, node/service.php):

• Comment targets are account and voting; rating scopes are account, forum and node.<name>
• Point::ACTIONS loses order (fourteen actions); a Node category may not take a forum category in use
• Favorites keep forum and Node types

4. Administration (admin/modules/*.php, modules/search, modules/voting, modules/account, modules/presentation):

• The setting amod is gone: nothing read it and three of its four options were removed modules
• Extra fields serve account and forum; ratings list account, forum and the Node types
• Search, newsletter, voting and the profile favorites lose their shop branches

5. Schema and update (setup/sql/table.sql, setup/sql/table_update6_3.sql, setup/index.php):

• table.sql drops auto_links, clients, clients_down, money, order, partners, products, whois and _referer.lid; the update file no longer touches those tables and drops lid
• The update preflight, the ratings unit and the fields unit forget order, clients, products and shop; a 6.2 shop rule counts as dropped, shop votes as foreign, and order fields stay positional
• The update drops amod from the site configuration and expects fourteen points actions

6. Shipped configuration, language and themes:

• config/modules, uploads, search, ratings, points, fields and global lose the removed modules
• 46 language constants that only the removed code read leave all six locales
• The lite theme loses the cart and shop hooks of its fragments, their CSS, the product, WebMoney and domain check menu items; the invoice tokens leave the frozen API roster by decision

7. Tests, tools and documentation:

• Tests that used the shop as a sample target move to voting, forum or a Node type; tests of the removed features are deleted; skipped tests fall from 28 to 4
• Label and theme baselines, upload route check, SEO audit and comment recount follow the tree
• UPGRADING.md gains a section on the removed modules; NODE, POINTS, RATINGS, TESTS and VERSIONS describe the current system

Benefits:

• The core carries no code for modules it does not ship
• An update from 6.2 no longer fails on a missing shop, order or whois table

Technical notes:

• Breaking: a site that needs these modules stays on its current release; the core has no hooks for them
• Breaking: the lite tokens --sl-invoice-width and --sl-invoice-logo-width are gone from the API
• Breaking: _referer.lid and the global setting amod are dropped; the tables of the removed modules stay on an updated site and are never read

The label crawl had been red since before Node: its baseline predated every Node page, so no new label defect could be told apart from the old ones. Three defects behind it are fixed and the baseline is taken again over the routes that exist today.

Core changes:

1. One id key for the select fragment (templates/lite/fragments/select.html, callers):

• The lite fragment read input_id while the admin one reads selectid, so a caller naming selectid left the site select without an id and its label pointing nowhere
  • Node categories, extra fields of Field and getTplCatSelect() on the site were affected
• Both fragments read selectid; account, contact, rss, Node and the category select pass it
• TemplateValidationTest holds both fragments and refuses input_id at any select caller

2. Hints of the Node admin forms (modules/node/admin/index.php):

• The poll, publish date, type name, extension and view mode hints carry an id, and their field names it in aria-describedby, as every other admin form already does

3. Accessible name of the code editor (core/classes/editor.php, plugins/editors/codemirror/driver.php):

• Editor::getCode() takes a label and falls back to _TEXT, as the content editors do
• CodeDriver::getWidget() receives it; CodeMirror writes it as aria-label of its content through EditorView.contentAttributes, JSON-encoded so a file path cannot close the inline script
• All nine code editors of the panel name their file, template, block, query or log
• EditorFormatTest drives the driver and refuses a caller without a label

4. Label baseline (tools/label-audit-baseline.json):

• Taken again as a first store: the routes of the removed modules no longer exist, which the crawl counts as fallen coverage and refuses to overwrite; 20 entries become 3
  • Kept: two duplicate ids of the security ban list, and the avatar hint of the settings tile, which is referenced by its radio group but sits outside the rows the crawl knows

Benefits:

• A click on a label focuses its select, and a screen reader announces field names and hints
• ui:label is green and can report the next regression

Technical notes:

• Breaking: CodeDriver::getWidget() takes a sixth argument string $label; a code editor driver of a third party must add it (UPGRADING.md, docs/EDITORS.md)
• The select fragment of the site no longer reads input_id