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

Content [tabs][tab] blocks and account tabs now emit the same data-attr tab contract as admin modules (data-sl-tabs-init / data-sl-tab-target / data-sl-tab-panel) instead of the legacy navi-tabs-wrap + anchor markup. This makes content tabs render and switch correctly under any theme, including the admin content preview that previously logged missing templates.

Core changes:

1. Tab builder (core/system.php):

2. getNaviTabs() builds links via tabs-link and panels via tabs-panel, wrapped by the shared tabs partial with is_runtime

3. Stable unique group id via a static counter, sanitized prefix/id

4. Plain titles escaped, HTML titles passed as raw label_html (behavior preserved from the old anchor builder)

Benefits:

• One tab contract across themes; admin preview no longer errors
• Robust against duplicate/empty ids

Remove the duplicate global "editor.admin" setting. The admin content editor is chosen per-admin (Administrators module); the main config keeps only the user editor. New or unset admins fall back to plain.

Core changes:

1. Config form (admin/modules/config.php):
2. Remove the admin content-editor select and its save handling
3. Saved editor config now holds only user + code
4. Default config (config/global.php):
5. Remove editor.admin (readers fall back to 'plain' via ?? 'plain')
6. Constants (admin/lang/*.php):
7. Remove the now-unused _EDITORADMIN constant across all six locales (keep _EDITORUSER)

Benefits:

• No duplicated admin-editor setting; single source is the per-admin profile
• Cleaner config surface

Technical notes:

• editor.admin readers keep the ?? 'plain' fallback; no behavior change beyond default = plain
• Generated config/local.php cache regenerates from global.php on next request

Add a dedicated "Редакторы содержимого" section to the config admin help describing the separate user/admin editor configs and how each editor stores and renders content.

Core changes:

1. Config help (admin/info/config/ru.md):
2. Explain separate editor.user / editor.admin configs and the per-admin override
3. Table of content editors (plain, toastui, tinymce, ckeditor) with roles and storage format
4. Describe processing model (escaping + parser vs trusted HTML) and [usehtml]/[usephp]
5. Note that TOAST UI has Markdown and HTML WYSIWYG modes, both saving Markdown
6. Clarify the code editor (CodeMirror) is separate, used for admin code/markup fields
7. Align label references with the new "Редактор пользователя" / "Редактор администратора"

Technical notes:

• Only opening/standalone BB tokens are shown; the parser would consume complete BB pairs

Restore the responsive content-image rules that were dropped: a thumbnail gallery component for content download lists and a width cap for parser images.

Core changes:

1. Images (templates/lite/assets/css/theme.css):
2. .sl-img: add max-width:100%; height:auto so parser/content images never overflow
3. Gallery (templates/lite/assets/css/theme.css):

4. Add .sl-gallery (responsive auto-fill grid), .sl-gallery-thumb (fixed-ratio contain box) and .sl-gallery-dl (download button), all on design tokens

Benefits:

• Content images stay within the layout (no horizontal overflow)
• Clean sl- gallery component for content download lists (replaces legacy .ms- markup)

The alignment BB-tags were processed inline, after the Markdown block parser had already split the text into paragraphs, so a multi-paragraph

never matched (open and close tags landed in different blocks) and the tags leaked into the output as literal text.

Core changes:

1. Parser (core/classes/parser.php):

2. Move [left/right/center/justify] handling to filterBbBlocks (block level), alongside [quote]/[hide], so the whole block is captured before paragraph splitting

   • Inner content is re-parsed via filterNest(), wrapping each paragraph correctly
   • Iterative while-loop to support nesting
3. Remove the old inline alignment handler
4. Tests (tests/Unit/ParserFixturesTest.php):

5. Add checkBbAlignBlockSpansParagraphs: multi-paragraph [justify] wraps each <p>, no literal tag remains; single-line [center] still works

Benefits:

• [justify]/[center]/etc. work across multiple paragraphs
• Alignment applied via a single text-align div, content fully parsed