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

Bring documentation in sync with the removal of the BB editor, the addition of Toast UI as the primary content editor, and the new theme hook architecture. Update admin info texts to remove outdated BB editor references.

Core changes:

1. docs/EDITORS.md:
2. Remove bbcode/ from the plugin directory tree
3. Update manifest.json example to reflect Toast UI (id, label, driver, formats)
4. Extend formats field description to include markdown as a valid value
5. docs/TEMPLATES.md:
6. Remove outdated note about legacy rendering and removed runtime files
7. Add templates/<theme>/index.php to the theme directory structure listing

8. Add full Theme Hooks section: purpose, loading mechanism, hook function contracts (getThemeHeadVars, getThemeFootVars, getAdminHeadVars), usage rules, and standard implementation direction

9. admin/info/config/ (de.html, ru.md, uk.html):
10. Replace BB editor editor list with current editors (ToastUI, TinyMCE, CKEditor)
11. Update _CLICABLEINFO hint to describe hyperlink conversion as editor-neutral
12. admin/info/uploads/ (de.html, ru.md, uk.html):
13. Replace references to BB Editor with editor-neutral wording in all three locales
14. admin/info/messages/ru.md, admin/info/newsletter/ru.md:
15. Replace «BB-редактор» references with neutral «редактор» wording
16. README.md:
17. Remove bbcode from the list of bundled editor drivers
18. New docs files:
19. docs/TODO.md: current open task list for the project
20. docs/admin-layout-demo.html: static HTML prototype of the admin layout
21. docs/admin-layout-demo-2.html: alternate admin layout prototype variant

Benefits: - Docs accurately reflect the active plugin set and theme hook contract - Admin info texts no longer reference the removed BB editor - Theme hook documentation provides a stable reference for custom theme authors

Technical notes: - admin/info files use locale-specific markup (BB-style for .html, Markdown for .md) - TEMPLATES.md hook rules section covers both do and do-not patterns

Update the admin theme visuals: a larger logo image replaces the old one, the toolbar becomes a flex row, and the admin footer gains a SLAED home link rendered through the standard link fragment.

Core changes:

1. templates/admin/images/slaedcms.png:
2. Replace 169×51 logo with a 256×73 higher-resolution version
3. templates/admin/images/000slaedcms.png:
4. Add the previous 169×51 logo as a preserved alternate (original dimensions)
5. templates/admin/assets/css/new.css:
6. Update .sl-admin-login-header height to 104px (was 82px) at all breakpoints
7. Update .sl-admin-login-header h1 a to 256×73 with background-size
8. Update .sl-admin-login-shell .sl-admin-brand height to match
9. templates/admin/assets/css/theme.css:
10. Update .header h1 a to 256×73 logo with background-size
11. Update .sl-admin-brand and .sl-admin-toolbar height to 90px (was 72px)
12. Set .sl-admin-toolbar to display:flex + align-items:center
13. Add .footer span a.sl-slaed-home { right: 62px } positioning rule
14. Add .footer span a.sl-slaed-home:before { content: "\f588" } icon
15. templates/admin/fragments/link.html:
16. Add is_top_hidden flag support: appends thide CSS class when set
17. templates/admin/partials/foot-controls.html:
18. Render brand_link via the link fragment when present (before the top link)
19. core/system.php:

20. renderFootControls(): add $withSlaedLink = false parameter; when true, inject a brand_link array with href=//slaed.net and class=sl-slaed-home

21. setFoot() admin path: pass true to renderFootControls() to show the link

22. Remove the legacy preview() compatibility wrapper (was unused after getTplBbEditor removal; getTplPreviewContent() is the direct call target)

Benefits: - Admin logo is crisp on high-DPI screens - Footer brand link uses the existing link fragment — no custom HTML - thide class is now driven by template data, not hardcoded conditionals

Technical notes: - is_top_hidden in link.html appends thide alongside any other class values - The brand link uses is_top_hidden: true so it renders as an icon-only link - preview() removal is safe: getTplPreviewContent() is the direct API

Rewrite getFallbackImage() to resolve the placeholder image using the active theme name instead of iterating a static list of hard-coded candidate paths. Add missing no-image.png assets for the default and simple themes.

Core changes:

1. core/classes/parser.php — getFallbackImage():
2. Use getTheme() or $conf['theme'] to determine the active theme at runtime
3. Build a deduplicated list of candidate themes (active → default → lite → admin)
4. Look for templates/<theme>/images/misc/no-image.png in each candidate
5. Use BASE_DIR for absolute path checks instead of $this->getRootPath()
6. Fall back to an embedded 1×1 transparent GIF if no file is found
7. New image assets:
8. templates/default/images/misc/no-image.png (951 bytes)
9. templates/simple/images/misc/no-image.png (951 bytes)

Benefits: - Fallback image resolution honours the active theme without a fixed path list - New themes are resolved automatically without editing the candidate array - BASE_DIR usage aligns with the rest of the codebase path handling

Technical notes: - Static cache ($fallback) preserved: resolution runs once per request - Embedded GIF fallback remains as last resort when no file exists on disk - templates/admin and templates/lite already had no-image.png; only default and simple were missing the asset

Implement the server-side file upload API for the Toast UI editor and wire it into the editor frontend. The new API handles file upload and file listing as dedicated endpoints in index.php, backed by focused helper functions in core/system.php. Custom JS and CSS assets extend the editor with emoji, icon styles, tag shortcuts, and upload panel integration.

Core changes:

1. core/system.php — editor JSON API helpers:
2. getEditorJson(array): emit JSON response and exit
3. getEditorUploadData(string): validate and return upload config for a module
4. checkEditorUploadAccess(string, array): check visitor upload permission
5. getEditorImageData(string, string, int, int): validate image dimensions
6. getEditorFileData(string, string): build file metadata row for JSON output
7. addEditorUpload(): handle POST file upload and return JSON result
8. getEditorFileJson(): return stored editor files as JSON for the file panel
9. index.php:
10. Route go=4 op=editorUpload to addEditorUpload()
11. Route go=4 op=editorFiles to getEditorFileJson()
12. Fix routing bug: switch($go) corrected to switch($op)
13. plugins/editors/toastui/driver.php:
14. Add getEmojiLabels(): inline locale-mapped emoji panel labels (de/en/fr/pl/ru/uk)
15. Load slaed-icons.css, slaed-tags.js, slaed-emoji.js, slaed-upload.js
16. Pass upload panel and JSON options (token, endpoints, labels) to JS via SlaedToastUi.register()
17. Render toastui-upload-panel partial when module upload is permitted
18. New Toast UI assets (plugins/editors/toastui/assets/):
19. slaed-emoji.js: emoji picker plugin with categorised emoji sets
20. slaed-icons.css: custom toolbar icon overrides using Bootstrap Icons
21. slaed-tags.js: tag shortcut extension for common BB-style tags
22. slaed-upload.js: upload panel logic (drag-drop, file list, attachment insert)
23. Upload panel partials (templates/*/partials/toastui-upload-panel.html):
24. Added for admin, default, lite, simple templates
25. Bootstrap Icons vendor (templates/default|lite/assets/vendor/bootstrap/):
26. bootstrap-icons.min.css and woff2 font file for the icon set

Benefits: - Toast UI now supports full file upload with the same access rules as the BB editor - Upload API is editor-agnostic: clean helper functions with no HTML coupling - Emoji, tags, and upload are modular JS extensions loaded only when needed

Technical notes: - Upload endpoints use the existing SLAED token system (getSiteToken/checkSiteToken) - addEditorUpload() handles multi-file upload arrays and returns per-file results - getEditorFileJson() respects user ownership and moderator scope limits - Bootstrap Icons font is vendored; no CDN dependency at runtime

The admin layout rendering functions (language switcher, top menu, layout variable assembly) were scattered across a theme-local hook file. They are now defined in core/admin.php, making them available to any admin theme without coupling logic to a specific theme directory.

Core changes:

1. core/admin.php — new layout helpers:
2. getAdminLanguageLinks(): renders the language switcher for the admin toolbar
3. getAdminTopMenu(): renders the admin top navigation for admin and moderator

4. getAdminLayoutVars(): returns the complete set of variables needed by any admin layout (menu, lang links, sidebar blocks, or login prompt)

5. templates/admin/index.php — deleted:
6. getAdminHeadVars() and getThemeFootVars() moved out of the theme hook
7. admin theme no longer requires PHP logic in templates/admin/index.php
8. core/system.php — theme hook integration:

9. Add getThemeHookVars(string $hook): array — safely calls optional theme hook functions and normalises the return value to an array

10. setHead(): use getAdminLayoutVars() + getThemeHookVars('getAdminHeadVars') instead of directly calling the removed theme hook function

11. setHead(): use getThemeHookVars('getThemeHeadVars') for frontend
12. setFoot(): use getThemeHookVars('getThemeFootVars') for frontend

Benefits: - Admin layout logic is now co-located with admin helpers in core/admin.php - Theme hook contract is narrowed: theme index.php is optional and additive - getThemeHookVars() eliminates function_exists guards at every call site - Cleaner separation between core rendering and per-theme customisation

Technical notes: - Templates/admin/index.php is now deleted; custom admin themes may still define getAdminHeadVars() in their own index.php if override is needed - getAdminLayoutVars() is safe to call unconditionally; it checks isAdmin() internally and returns only login text when the user is not authenticated - No change to the rendered output for default admin theme installations

Remove the BBcode editor plugin and all related artifacts from the codebase. The BB editor has been fully replaced by Toast UI and is no longer active. All CSS, images, upload panels, and lang constants tied to the BB editor are deleted to eliminate dead code and reduce maintenance surface.

Core changes:

1. BB editor plugin (plugins/editors/bbcode/):
2. Remove driver.php and manifest.json
3. BB editor assets (templates//images/editor/, /partials/):
4. Delete bb-editor.png sprite and index.html from admin, default, lite, simple
5. Delete editor-upload-panel.html from default, lite, simple
6. Delete deprecated forum banner images from templates/lite/images/banners/
7. BB editor CSS (templates/admin|default|lite/assets/css/system.css):

8. Remove .sl_bb-editor, .sl_bb-panel, .sl_bb_*, .sl_bbup-panel, .sl_bb_trans and related rules from all three themes

9. Lang constants (lang/.php, modules/jokes/lang/.php, admin/lang/*.php):

10. Remove 20 BB editor toolbar constants (_EBOLD, _EBREAK, _ECENTER, _ECOLOR, _EEMAIL, _EHR, _EITALIC, _ELAT, _ELEFT, _ELI, _EMINUS, _EPLUS, _ERIGHT, _ERUS, _ESIZE, _ESMILIE, _ESTRIKET, _EUNDERLINE, _EURL, _EYUSTIFY)

11. Remove 7 auxiliary editor constants (_FONT, _JERROR, _JINFO, _JQUOTE, _JTYPE, _UPLOADINFO, _UPLOADFINISHJ) from all 6 locales

12. Update _CLICABLEINFO in admin/lang/*.php to remove BB editor reference
13. getTplBbEditor helper (core/helpers.php):
14. Remove the 193-line BB editor rendering function
15. Config (config/local.php):
16. Update base_fingerprint after asset removal

Benefits: - Eliminates ~700 lines of dead code and sprites - Removes 20+ unused lang constants from 6 locale files - Cleans BB editor CSS rules from all active theme stylesheets - Reduces cognitive overhead when working with the editor subsystem

Technical notes: - No runtime behavior change; BB editor was already superseded by Toast UI - All BB editor constants verified unused across PHP, HTML, JS, and template files - _CLICABLEINFO updated to be editor-neutral (applies to any content editor)

Frontend-Fragmente (default/lite/simple) bekommen zusätzliche semantische Flags — span, button, input, link, table, title, code-row. Das Fragment content-block wurde in block-content umbenannt und leicht erweitert. Neu ist ein minimales partials/div.html. Das Partial block-user-info.html trennt Begrüßung in zwei separate Felder (greeting_label + greeting_name) statt eines vorformatierten HTML- Strings. Alle Aufrufer in blocks/, core/, modules/*/index.php wurden konsequent umgestellt.

Core changes:

1. Fragment-Rename (alle 3 Themes):
2. content-block.html gelöscht, block-content.html neu angelegt

3. Selbe Logik + neue Flags (z.B. is_signature, is_center, is_radio_group), synchron mit Admin-Theme für einheitliche Fragmentnamen

4. span.html (default/lite/simple):

5. +is_form_value, is_views, is_line_stack_item, is_cat_image, is_cat_name, is_new_today, is_new_days, is_new_week

6. Ersetzt inline class="sl_n_day" etc. durch semantische Flags
7. button.html:

8. +is_reload_query-Trigger mit htmx-Swap, is_legacy_green, is_back, is_navi_lower, is_login_submit

9. Button-/Input-Varianten konsolidiert
10. input.html:
11. +is_form_control, is_user_search, is_search_filter
12. Default-Klasse sl-field nur bei Abwesenheit anderer Klassenflags
13. link.html:

14. +is_shop_add (sl-shop-add), is_bold_label Bold-Linklabel, suffix_html für nachgestellte Badges/Icons (z.B. NewGraphic)

15. code-row.html:
16. row_class optional — is_odd → sl-code-row-odd / sl-code-row-even
17. table.html / table-row.html:
18. is_col_half im Header, is_hidden und is_forum_stat auf Row-Level
19. fl-col-stat Spalte für Foren-Statistiken
20. title.html:
21. +is_plain für class="title" statt sl-title (ältere Themes)
22. partials/block-user-info.html:

23. greeting (HTML-String) → greeting_label + greeting_name (zwei Felder). Begrüßung wird jetzt im Template zusammengesetzt, nicht in PHP

24. partials/div.html (neu, default/lite/simple):

25. Minimaler generischer Div-Wrapper für einheitliche Semantik zwischen Themes

26. partials/form-add.html:
27. +is_calculator (sl-calculator-form)
28. Blocks (blocks/*.php):

29. auto_links, center, center_forum, center_media, center_plus, forum, img, languages, links, login, modules, user_info: alle Aufrufe von getHtmlFrag('content-block', ...) → getHtmlFrag('block-content', ...)

30. user_info.php: greeting → greeting_label/greeting_name, passend zum neuen block-user-info-Partial

31. Semantische Flags ersetzen hardkodierte class-Werte (z.B. 'class' => 'sl-shop-add' → 'is_shop_add' => true)

32. Core (core/helpers.php, core/system.php, core/user.php):

33. getTplRadioGroup(), getTplNewGraphic(), Footer-/Nav-Helper: content-block → block-content, Flag-basierte Klassen

34. getTplFieldsIn(): leerer input_class entfernt (unnötig)

35. getTplPager(): prefix als hartkodierter Leerstring (ungenutzte Option entfernt)

36. Module (modules/*/index.php — account, changelog, clients, contact,

content, faq, files, forum, help, jokes, links, main, media, money,
news, order, pages, rss, search, shop, voting, whois):

• getHtmlFrag('content-block', ...) → getHtmlFrag('block-content', ...)
• 'class' => 'sl-shop-add' / 'sl-section' / 'sl_n_day' → Flag-Form

• modules/shop/index.php: title_text nicht mehr per cutstr() beschnitten — Truncation erfolgt jetzt CSS-seitig

Benefits: - Einheitlicher Fragmentname block-content im Frontend und Admin - Keine hardkodierten Klassennamen mehr in PHP für wiederkehrende Varianten (is_new_today, is_shop_add, is_section, ...) - block-user-info-Partial kann Begrüßung lokalisierungsfreundlich ohne HTML-Verkettung in PHP aufbauen - Fragmente in allen 3 Themes synchron — leichter zu warten

Technical notes: - content-block.html in default/lite/simple in diesem Commit gelöscht; alle Aufrufer sind bereits auf block-content umgestellt - Frontend-Fragmente syntaktisch 1:1 identisch zwischen den 3 Themes (Theme-spezifisches Styling über CSS, nicht Template-Variation) - Rückwärtskompatibilität: keine — Template-/Parameter-Namen ändern sich, nur innerhalb des neuen Refactor-Strangs verwendet

Admin-Tabellen werden jetzt über semantische Spalten-Flags (is_col_id, is_col_check, is_col_author, is_col_status, is_col_actions, is_col_date, is_col_count) gestylt — hardkodierte class_name-Werte in PHP entfallen. Die Fragmente button, inline-badge, input, select, textarea, label bekommen zusätzliche Varianten-Flags (is_green/is_blue/is_plain, is_note/is_dimmed/is_success, is_inline_gap/is_search_filter etc.). Das Fragment content-block wurde in block-content umbenannt und um is_section und is_sidebar_count_list erweitert.

Core changes:

1. Fragment-Templates (admin/fragments):

2. block-content.html: ersetzt content-block.html + neue Flags is_section (→ sl-section), is_sidebar_count_list

3. table-cells.html + th.html: neue Spalten-Flags is_col_id (sl-col-id), is_col_check (sl-col-check), is_col_author (sl-col-author), is_col_status (sl-col-status), is_col_actions (sl-col-actions), is_col_date (sl-col-date), is_col_count (sl-col-count)

4. table-row.html + div-row.html: is_lang_edit, is_ratings_inner, is_hidden für Row-State-Klassen

5. button.html: is_green/is_blue/is_plain lösen veraltete is_chlog_primary/is_chlog_secondary für Button-Varianten ab

6. inline-badge.html: +is_note/is_dimmed/is_success/is_danger/ is_action_label/is_muted/is_green/is_red/is_category/ is_views/is_post_icon/is_date + color_attr für Inline-Style

7. input.html: +is_config/is_ratings_days/is_form_control/ is_inline_gap/is_search_filter/translate_target

8. select.html: +is_inline_gap/is_search_sort/is_search_order/ is_search_filter

9. textarea.html: +is_config
10. label.html: +is_associated_option
11. Partials (admin/partials):
12. div.html: +is_search_line, is_rate_box (für Ratings-Tab-Layout)
13. form.html: +is_inline_filter (Such-Filter-Formulare)

14. basic-monitor.html: Prüfstatus-Styling auf semantische Badges umgestellt

15. Layout (admin/layouts):

16. admin.html: <main class="sl-admin-content"> bekommt inneres <div class="sl-admin-content-inner"> für Grid/Flex-Container

17. Styles (admin/assets/css):

18. new.css: neue .sl-col-*-Regeln (Breite + Alignment für ID/Check/Author/Status/Actions/Date/Count-Spalten), .sl-section, .sl-inline-gap, .sl-search-filter-field, .sl-lang-edit-row, .sl-ratings-inner-row, .sl-associated-option

19. theme.css: minimale Layout-Anpassung für sl-admin-content-inner
20. Core + Module (core/admin.php, admin/modules/, modules//admin/):

21. Alle Aufrufe von getHtmlFrag('content-block', ...) auf getHtmlFrag('block-content', ...) umgestellt

22. class_name => 'sl-col-id' und ähnliche auf Flag-Form ('is_col_id' => true) migriert — gilt für alle Admin-Tabellen in admins, comments, config, database, favorites, groups, lang, messages, modules, monitor, newsletter, ratings, scheduler, statistic sowie alle modules/*/admin/index.php

Benefits: - Spaltenbreiten/-Ausrichtung deklarativ in CSS statt verstreut in PHP - Konsistente Button-/Badge-Varianten ohne Zeichenketten-Klassennamen - Ein einziger Fragmentname (block-content) statt gemischter content-block-Nutzung - Klarere Trennung von Admin-Spalten-Semantik und freien Klassen

Technical notes: - content-block.html im admin-Theme wird in diesem Commit gelöscht; alle Aufrufer sind bereits auf block-content umgestellt - is_*-Flags sind additiv kombinierbar; Reihenfolge im Template bestimmt die CSS-Klassen-Reihenfolge - color_attr in inline-badge ersetzt Inline-<span style="color:..."> und erlaubt beliebige Hex/CSS-Color-Werte

Nach dem Block-Refactor (Commit 2ff47e47) nutzten die neuen atomaren Fragmente bereits die Klassen sl-block, block-modules, block-flags, block-menu, block-login etc., doch die zugehörigen CSS-Regeln waren in den Themes nicht vorhanden. Ohne diese Styles fielen Sidebar-Blöcke wie modules.php in rohen Inline-Fluss und «verschluckten» visuell die nachfolgenden Blöcke — auf einer frischen Installation war faktisch nur der Inhalt des languages.php-Blocks sichtbar.

Core changes:

1. Block-Wrapper (sl-block, sl-block-content):

2. sl-block: Hintergrund #f6f8fa, padding 15px, border-radius 8px, margin-bottom 25px (Visuelles Äquivalent zur alten .block-Regel in blocks.css, aber für das neue <aside class="sl-block">-Markup)

3. sl-block-content: line-height 1.4 für lesbare Block-Inhalte
4. #sidebar .sl-block:last-child: kein margin-bottom (letzter Block)
5. modules.php (block-modules, block-mod-section):

6. .block-modules: flex-column mit 4px gap — Navigation als saubere vertikale Liste statt Inline-Fluss

7. .block-modules .sl-module: display:block + padding 4px 2px für klickbare Zeilen

8. .block-mod-section: Separator + kleinere Schrift für Moderator- Unterabschnitte (invisible/inactive Modules, Admin-Bereich)

9. languages.php (block-flags):

10. .block-flags: flex-wrap mit 6px gap, align-items center — Flaggen flüssig nebeneinander mit sauberen Abständen

11. .block-flags a: display inline-flex für konsistente Vertikalzentrierung
12. login.php / user_info.php (block-login):
13. .block-login p: margin 6px 0 — Zeilenabstände im Login-Formular
14. .block-login input: margin 3px 0 — vertikaler Breathing Space
15. menu.php (block-menu):

16. .block-menu ul: list-style none, padding 0, margin 0 — DB-Menü ohne Standard-Listendarstellung

17. .block-menu li: margin 4px 0 — Abstand zwischen Menüpunkten

Benefits: - Frisch installierte Sidebar-Blöcke rendern sichtbar und nicht mehr als zerfließender Inline-Text - Visuelle Parität zur alten .block-Regel ohne Markup-Rückportierung - Konsistente Klassen in default/lite/simple — ein einziger Styleset für alle drei Frontend-Themes

Technical notes: - Rein additiv: keine bestehenden Regeln geändert oder entfernt - Legacy-Regel .block in blocks.css bleibt unberührt für evtl. noch nicht migrierte Templates - TODO aus Commit 2ff47e47 erledigt: "Neue sl-*-Klassen (block-login, block-flags, block-menu) in new.css zu ergänzen"

Fingerprint spiegelt den aktuellen Stand nach Einführung der Table- Fragment-API (is_truncate/is_fixed) und der Admin-Login-Auth-Form- Vereinheitlichung wider.