The stored texts are Markdown since the update converts them, so the writers stop escaping what they store and the parser stops reading the BB it no longer meets: every store keeps the typed text, the editor mounts it unchanged, the bracket layer reads [hide], [tabs], [attach], [usehtml], [usephp] and [block] alone. The full run of update.php on a copy of the production dump found two faults of the updater and the writers; both are fixed, the run is proven, and what lasts of it is reference in docs/.

Core changes:

1. One storage of a typed text (core/security.php, core/classes/, core/helpers.php, core/user.php, admin/modules/, modules/):

2. filterSourceText() turns a typed text into the stored source: CRLF to LF, the trusted tags, the censor list, never HTML-escaped, as the parser escapes at render

   • the blocks, the admin messages, the newsletters, the signatures and own blocks, the contact text, the forum, the

comments, the private messages and Node read the field raw and store through it

• Comment and Privat lose their own copies of the censor (filterCommentBody(), filterMessageText())

• getTplTextarea() mounts the stored source as it is: no <br> turned into a hard break, no entity decoded

• The forum, the signatures, the own blocks, the blocks, the admin messages, the newsletters, the contact text and the preview of the editor render safe with trust, as a Node material does

• The reply quote of a private message and of a forum post quotes the stored Markdown as it is

• The admin message form keeps an empty language; the snippet of a private message drops the quote markers of every depth and the escapes (filterSnippet() of Privat)

• The parser reads the SLAED tags alone (core/classes/parser.php, public/templates/*/fragments/, lang/):

• The handlers of the converted and removed BB tags, ed2k and the smilies go, with images/smilies/ of both themes and _SMILIE of the six lang files

• parser-inline.html, parser-block.html, parser-image.html and blockquote.html of both themes lose the parts only those tags drew

• The read-only editor (core/classes/editor.php, public/plugins/system/editor.js, fragments/editor-*.html, theme.css):

• Editor::getFrame() takes readonly; the frame marks its area, the kit marks every tool that changes a text with the need edit, and editor.js keeps CodeMirror read-only and without files

• .sl-markdown table of the admin theme draws the tables of the help
• The update (public/update.php):

• Points, ratings and fields whose mark is set and whose manifest is missing ran on the site before and answer done; they stopped the whole run on production, so no table was dropped

• The guard of getMigrateAttach() keeps an image inside a link to another site with text or a hard break beside it in the label, so a repeat no longer rewrites it

• The comment edit form of the panel (admin/modules/comments.php):
• The author and the IP are escaped once
• Help and documents (admin/info/, modules/contact/admin/info/, docs/):

• The help of the configuration, the blocks, the admins, the comments, the monitor and the contact text in the new state, the tables of the help readable

• docs/PARSER.md: the engine, the measurement, the grammar of the SLAED tags, what is no markup and the conversion of the BB era; docs/EDITORS.md: the stored text on mount and save

• docs/NODE.md: a site of an early 6.3 build, its folder moves, the address step of the migration, the columns no parser call renders; docs/UPDATE.md: moving slaed.net to 8.0, from the copy to the live check

• docs/VERSIONS.md: both changes
• Tests (tests/):

• ParserFixturesTest without the BB fixtures, EditorBreakTest on the storage of every writer, EditorFormatTest on the read-only frame, PrivatClassTest on the snippet

• UpdatePointsTest, UpdateRatingsTest, UpdateFieldsTest on a mark without a manifest, UpdateAttachTest on the label around a linked image

Benefits:

• A save without a change keeps every byte of a text; what an author types is what the store keeps
• One rendering path for every Markdown text of the site
• The move of slaed.net is a proven, repeatable run with its order written down

Technical notes:

• Breaking: [u], [color], [size], [family], the alignment tags, the alignment of an image, ed2k and the smilies - keep their text and lose the formatting; images/smilies/ and _SMILIE are gone

• No schema change; the stored texts were converted by the text unit of update.php

The places of a block listed the site modules alone, so a block could not be shown on the pages of one Node type: those pages carry the name of their type in $name, and the module node itself is never a page name. The list now offers every type beside the modules.

Core changes:

1. The places of a block (admin/modules/blocks.php):
2. getBlockWhereItems() lists the site modules and every type of config/node.php, sorted by name, and leaves "node" out
3. The popover of a box names what it is, module or type, with its code
4. Help (admin/info/blocks/ru.md):
5. The places list the modules and each type, and a block marked at a type shows on the pages of that type
6. Tests (tests/Unit/NodeIntegTest.php, tests/Support/route_probe.php):
7. The block form offers the type "docs" and no "node", and a save keeps the type the block was bound to

Benefits:

• A block meant for documentation or news pages shows there and nowhere else, without a module of its own

Technical notes:

• The stored value is the same list of names in _blocks.which; a type name is matched as the page name already is

The stored texts are moving off BB onto Markdown, so the parser that renders them has to read Markdown by the standard and not by its own habits. The examples of both specifications are now fixtures, and the parser was rebuilt on a block tree and an inline tree until every one of them passes in the trusted and in the safe mode.

Core changes:

1. Conformance fixtures (tests/Fixtures/spec/, tests/Unit/ParserFixturesTest.php):

2. commonmark.json holds the 652 examples of spec.json 0.31.2 as published, gfm.json the 24 extension examples of GFM 0.29-gfm (cmark-gfm 0.29.0.gfm.13), the two task list examples marked disabled there included

3. filterDocMeetsTheSpec() runs every example at $safe = false, and at $safe = true every one but those carrying raw HTML or a link of a scheme the safe rendering refuses

   • the comparison removes only the markup of the theme: heading ids, theme classes, the code figure, the

broken-image fallback, the cell alignment style and the disk check of a local image (Parser::$fileoff)

• the CommonMark examples run with the tag filter and the extended autolinks off (Parser::$gfmoff), the GFM ones

with them on, as the spec runner of cmark-gfm does; code is measured in the shipped highlighter mode 2

• failing.json is the baseline of examples that fail; a listed example that passes fails the test, so the list only shrinks, and it is empty: trusted 676 of 676, safe 591 of 591

• The engine (core/classes/parser.php):

• getBlockTree() reads the block structure one line at a time: indented and fenced code, HTML blocks of the seven kinds, link reference definitions, setext headings, lazy continuation, tight and loose lists, GFM tables

• getInlineTree() reads inline content with the delimiter and bracket stacks of the specification: flanking rules, code spans, references, autolinks, entities, hard breaks, GFM strikethrough and extended autolinks, mark

• getBlockHtml() and getInlineHtml() render the tree through the fragments; the regex passes filterCode(), filterBlocks(), filterList(), filterTable() and the Markdown tail of filterBbInline() are gone

• The bracket layer reads the copy of filterMask(), which a scan of the same parse masks; a raw pair whose opener the scan leaves visible is taken back whole, since its content is no Markdown

• A safe rendering keeps an address without a scheme and one of http, https or mailto; data:, javascript: and vbscript: die in every mode; a line of <br> opens an HTML block as any complete tag does

• Parentheses in a link target are bounded at 32 levels, as cmark bounds them
• Fragments of both themes (public/templates/*/fragments/):
• list takes has_start and start_num for <ol start>, parser-table drops <tbody> without body rows
• Documents (docs/PARSER.md):

• The standard, the comparison, the SLAED extensions on top of it and the bracket layer; the Markdown list names everything CommonMark and GFM define; the safe and the trusted mode as the engine reads them

Benefits:

• A text renders as every CommonMark and GFM tool renders it, which the conversion of the stored BB relies on
• The two known defects are gone: fenced code inside a quote or a list item, and <https://...> and <name@host>

Technical notes:

• Measured on the 28344 renderable texts of the stand: both parsers render them in the same time (8 to 10 s), the slowest text 43 ms, no warning; 6637 render differently, each by the standard

• The plain format keeps its own path; no render call of the site passes it

The production site runs a development build of early October whose Node texts point into the archive of the first migration and whose schema, settings and tables lag behind the release. update.php now brings such a site forward on a copy without migrating its content again, drops the tables of the modules gone for good and every source table whose rows are in Node, and carries jokes and media into Node for any other 6.2 site.

Core changes:

1. Catch-up of a 6.3 site (public/update.php, storage/update/sql/table_update6_3.sql):

2. setUpdateArchive() rewrites the uploads/archive/<module>/ and old folder addresses of Node texts and their comments into [attach] or the file address of the material, and an archive address elsewhere into the address of the published material that carries the name

   • a dry run (POST dry=1, "Count the file addresses") counts per column and writes nothing
   • a manifest with counts, cursors and state; a stopped run continues, a verified unit is skipped

3. setUpdateMerge() takes the retired keys out of a 6.3 site and adds every shipped option it lacks from storage/backup/release/config/; without that folder the step refuses

4. The eight time columns of the early-October tables reach the forms of table.sql through runiftype(), each moment kept; a 6.3 db.php is written in the collation of the release

5. Drop of the tables (public/update.php):

6. setUpdateTables(), at the end of the first stage, drops the tables of auto_links, clients, clients_down, money, order, partners, products and whois, and every source table of Node whose rows are all materials

   • a published row by its _node_legacy row, a pending row by a material of its type with its title and creation time
   • an empty table at once; a table with a row matched by neither stays, the report names up to ten ids

7. deleteMigrateTables() drops the table of a module right after its data step, once every row is a key of the map of the manifest and every material of the map is in _nodes; a manifest of another database keeps the table with a note

8. The page of the second stage shows a carried module from its manifest
9. Jokes and media (public/update.php, storage/update/sql/table_update6_3.sql):
10. Both join getMigrateMap(); "Batch X" renames their 6.2 columns

11. The twelve own columns of media land in the extra fields of its profile, every http(s) address of its links becomes a resource of the download role, ed2k and other schemes leave a note

12. The rating balances of both are carried
13. Text of the second stage (lang/*.php):
14. _NODE_MIGINFO says that the table of a module is dropped once its materials are carried, in all six locales
15. Tests (tests/):

16. UpdateArchiveTest with the archive unit, the settings merge and the drop on a site of early October (a cp1251 table, a pending row, a row no address names)

17. The update62 fixture gains the 6.2 tables of jokes and media with a rated joke and a film; UpdateSiteTest checks their materials, fields, resources and ratings, the tables left after each stage, and a stale table that stays

18. The probe adds its help request before the first run, because an empty source table drops there
19. SchemaUpdateValidationTest skips jokes and media like the other source tables
20. isTreeSkipped() no longer enters uploads/, whose copy of a site carries the PHP of old releases; TreeWalkTest holds it
21. Reference (docs/NODE.md):

22. The run order, the schema file, the tests and the migration of the removed modules describe the catch-up, the drop and the two new modules

Benefits:

• The production database moves to the current code keeping every row and id it holds
• No table of a gone or carried module is left behind, and none is dropped while a row of it is not in Node

Technical notes:

• Drops tables with no archive: the gone modules for good, the source tables only once their rows are materials
• update.php remains the maintainer's tool and is not shipped in a release

The multi-line comment blocks left in the remaining classes of core/classes/, the modules and panel screens, the CSS of both themes, the PHP entries and the JavaScript the release writes itself are cut to the one line the comment rule asks for: a fact outside the code, a decision that looks like a mistake, or a change that must not be made. With this commit no multi-line block is left; no line of code changed.

Core changes:

1. Remaining classes of core/ (core/classes/.php, core/classes/api/.php, core/system.php, core/apply.php, core/rescue.php):

2. the parser, feed, field, point, rating, cache, backup, editor, update, template, logger, quick, pdo and route classes and the API router and error cut to one line per function

3. core/system.php, core/apply.php and core/rescue.php lose the blocks that retold their code

4. Modules and panel screens (modules/account, modules/forum, modules/presentation, modules/search, admin/modules/config.php, fields.php, monitor.php, newsletter.php):

5. the blocks above the handlers of the modules and of the four panel screens cut to one line
6. modules/presentation/index.php: the block of 26 lines above the collector of the page figures cut to one line
7. CSS of both themes (public/templates/admin/assets/css, public/templates/lite/assets/css, the Toast UI skins):
8. base.css, theme.css, dock.css, presentation.css and the two skin.css files keep one line where a rule needs a reason
9. reasoning that retold the declarations below it, measurements of past rig runs and history are gone

10. Entries and own JavaScript (public/index.php, public/admin.php, public/templates/lite/index.php, public/plugins/system/*.js, public/plugins/presentation/presentation.js, public/plugins/altcha/altcha-init.js, the two CodeMirror build modes, public/templates/admin/assets/js/admin-ui.js):

11. the blocks of the two PHP entries and of the theme entry cut to one line

12. slaed.js, filemanager.js, emoji.js, global-func.js, presentation.js, altcha-init.js and admin-ui.js keep one line per function

Benefits:

• A comment line is a claim worth checking rather than a retelling to skip
• The comment rule now holds across the whole release, PHP, CSS and JavaScript alike

Technical notes:

• Comments only: with comments and whitespace removed, HEAD and the commit are identical in all 51 files
• php -l passes on the 33 PHP files
• No schema, URL, API or behaviour change