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

Auto-generated base_fingerprint reflects the new template file set introduced by the new/ fragment layer across all three themes.

Core changes:

1. config/local.php:
2. Updated: base_fingerprint to current codebase state

Benefits: - Config stays in sync with deployed template files

Technical notes: - Fingerprint is computed automatically on template structure changes

Replaces legacy content-card/content-view/liste-wrap/liste-basic fragments with new/ layer equivalents. Fixes admin URLs. Adds CSRF token to frontend delete links. Adds refer=2 support to admin actions() so frontend-initiated deletes redirect back to the frontend.

Core changes:

1. Card grid view (modules/news/index.php — news()):
2. Card: getTplContentCard → $tpl->getHtmlFrag('new/card', ...)
3. Fixed: edit URL op=news_add → name=news&op=add
4. Fixed: delete URL op=news_admin&typ=d → name=news&op=actions&typ=d
5. Added: refer=2 and CSRF token on frontend delete link
6. Alert: alert → new/alert
7. Liste view (modules/news/index.php — liste()):
8. Table: liste-wrap → new/table (5 cols: id/title/cat/poster/date)
9. Rows: liste-basic → new/table-row-liste
10. Letter nav: extracted from liste-wrap param to standalone output
11. Alert: alert → new/alert
12. Full view (modules/news/index.php — view()):
13. Renderer: getTplContentView → $tpl->getHtmlFrag('new/view', ...)

14. Removed HTML from PHP: <br><br> separators between hometext, bodytext and fields replaced with direct concatenation

15. Fixed: edit URL op=news_add → name=news&op=add
16. Fixed: delete URL op=news_admin → name=news&op=actions with token
17. Admin actions handler (modules/news/admin/index.php):
18. Added: $refer_val to distinguish refer=1 (admin tab) vs refer=2
19. refer=1 → admin panel status=1 tab (pending news, unchanged)
20. refer=2 → index.php?name=news (frontend list page)

Benefits: - No HTML strings in PHP — all markup in fragments - Admin URLs follow consistent name=MODULE&op=ACTION pattern - Frontend delete secured with CSRF token and refer redirect

Technical notes: - news/view() fields appended to rawtext (no separate fields param) - new/card.html reuses all sl-* classes defined in new.css - new/table-row-liste.html covers 5-column liste layout

Replaces legacy content-list and title fragments with new/ layer equivalents. Fixes admin URLs to match the name=content&op=action pattern. Adds CSRF token to frontend delete links. Fixes refer redirect in the admin delete handler so frontend-initiated deletes return to the frontend, not the admin panel.

Core changes:

1. Frontend list view (modules/content/index.php — content()):
2. Table: content-list-open → new/table (sortable, col_id/title/func)
3. Rows: content-list-basic → new/table-row-content with new/tip
4. Pager: setArticleNumbers → getTplPager with prefix new/
5. Alert: alert → new/alert
6. Removed: body from SELECT (unused in list)
7. Fixed: duplicate ?? fallback in config reads
8. Frontend view (modules/content/index.php — view()):
9. Renderer: title+filterDoc echo → new/view fragment
10. Removed HTML from PHP: fields separator moved to template
11. Fixed: rss_read result stored in $rss, not $conf['content']
12. Added: CSRF token on delete link, is_moder edit/delete nav
13. Admin delete handler (modules/content/admin/index.php):
14. Added: $refer flag (GET refer=1)

15. Redirect: refer=1 → index.php?name=content (frontend) otherwise → admin.php?name=content

Benefits: - No HTML strings in PHP — all markup in fragments - Admin URLs follow consistent name=MODULE&op=ACTION pattern - Frontend delete secured with CSRF token

Technical notes: - new/view.html handles fields via {% if fields %}<br><br>{{{ fields }}} - Admin refer flag mirrors pattern used in news module (refer=2)

Frontend modules using the new/ template layer need to call pager-link, pager-dots, and pager fragments from the new/ subdirectory. The prefix option allows callers to pass 'new/' and get new-layer fragments without duplicating pager logic.

Core changes:

1. getTplPager (core/helpers.php):
2. Added: $prefix = (string)($opt['prefix'] ?? '')
3. Changed: pager-link, pager-dots, pager fragment calls now use $prefix
4. Closure captures $prefix via use() for link rendering
5. Added missing space after current page number for consistent spacing

Benefits: - No duplicate pager code for new/ vs legacy fragment paths - modules/content/index.php and future modules pass prefix: 'new/' - Legacy callers unaffected (prefix defaults to empty string)

Technical notes: - Fragment path: $prefix.'pager-link' resolves to 'new/pager-link' - Space after current page item aligns with non-current item spacing

The sl-fullview article in new/view.html already renders a <hr> element before the footer buttons, making the CSS border-bottom on .fullview produce a visible double line.

Core changes:

1. theme.css — .fullview (templates/default/assets/css/theme.css):
2. Removed: border-bottom: 1px solid #ebebee
3. Kept: padding-bottom: 25px
4. theme.css — .fullview (templates/lite/assets/css/theme.css):
5. Same change applied

Benefits: - Single visual separator (the <hr>) in full article view - Eliminates visible double-line regression in default and lite themes

Technical notes: - Legacy .fullview class still used by old content-view.html fragments - new/view.html uses sl-fullview — border handled by <hr> in markup

Introduces a unified new/ fragment namespace for all frontend modules. All fragments use sl-* CSS class naming (hyphen), defined in new.css alongside the sl_* legacy classes in system.css/theme.css.

Core changes:

1. New fragment set (templates/*/fragments/new/):
2. alert.html — inline alert block (warn/info variants)
3. card.html — article card for grid layouts (sl-post sl-card)
4. navi.html — frontend navigation menu (sl-navi-menu)
5. pager.html, pager-link.html, pager-dots.html — paginator
6. table.html — sortable table wrapper with optional columns
7. table-row.html — generic table row wrapper
8. table-row-content.html — standard 3-column article row
9. table-row-liste.html — 5-column liste row (title/cat/poster/date)
10. tip.html — hover tooltip with date and read-count
11. view.html — full-page article view (sl-post sl-fullview)
12. New CSS layer (templates/*/assets/css/new.css):
13. sl-post, sl-card, sl-fullview, sl-title, sl-meta, sl-meta-foot
14. sl-entry-content, sl-rate-box, sl-pull-right
15. sl-table, sl-table-head, sl-table-body, sl-table-cell, sl-table-col-num
16. sl-pager and all pager sub-elements
17. sl-navi-menu
18. Applied identically to default, lite, and simple themes

Benefits: - Single source of truth for new-layer class naming across all themes - No HTML in PHP — all presentation moved to fragments - Clear separation: sl- (new.css) vs sl_ (legacy)

Technical notes: - Fragments deployed identically to all three themes (default, lite, simple) - new.css comments follow admin new.css style (simple slash-star groups) - Backward compatible: legacy fragments untouched

Adds two new architecture reference documents for subsystems introduced in the editor system migration. These files are referenced in the README documentation table and describe the stable contracts that contributors should follow when extending or integrating editors and the content parser.

Core changes:

1. docs/EDITORS.md:
2. Describe the pluggable Editor class architecture and manifest.json format
3. Document ContentDriver and CodeDriver interfaces
4. List bundled drivers and their intended roles
5. docs/PARSER.md:
6. Describe Parser class and filterContent() API
7. Document filterMarkdown() legacy shim and migration path
8. Clarify safe vs. unsafe parsing contexts

Benefits: - New contributors have a single reference for editor and parser integration - Eliminates undocumented API surface for two actively used subsystems

Technical notes: - Documents describe current repository state only; no forward-looking promises

Updates the active editor driver implementations for CKEditor, TinyMCE, ToastUI, and plain editors to align with the pluggable Editor class contract. Adds the BBCode driver as a new bundled content editor option. Updates TinyMCE and ToastUI to include current asset bundles.

Core changes:

1. Editor drivers (plugins/editors/):

2. ckeditor: update driver.php and manifest.json for current CKEditor 5 * Add bundled CSS asset (ckeditor.bundle.css)

3. tinymce: update driver.php and manifest.json; add current theme/model assets
4. toastui: update driver.php and assets; add i18n support and full JS bundle
5. plain: update driver.php for current Editor class interface
6. bbcode: add new bbcode driver (driver.php, manifest.json, assets)
7. Database schema (setup/sql/table.sql):
8. Apply pending schema updates matching current runtime expectations

Benefits: - All active editor drivers implement the ContentDriver interface correctly - BBCode editor available as a bundled option for user-facing content - ToastUI i18n bundle enables locale-aware Markdown editing

Technical notes: - Driver interface: getAssets(profile) + getWidget(id, name, value, profile, data) - manifest.json format unchanged; new drivers follow existing schema

Both standalone directories are superseded by the pluggable editor system. The TinyMCE 4.5 driver is now bundled in plugins/editors/tinymce/ with a current version and manifest. The filemanager plugin had no active callers after the textarea() editor dispatch migration and was confirmed unused.

Core changes:

1. Legacy file manager (plugins/filemanager/):

2. Remove entire ResponsiveFilemanager bundle (PHP backend + JS + assets) * No active references remain in core, admin, or module code after migration * File upload paths now go through the module-level upload handlers

3. Legacy TinyMCE standalone (plugins/tinymce/):

4. Remove TinyMCE 4.5.6 standalone bundle * Active TinyMCE driver is in plugins/editors/tinymce/ with current version * Old bundle used Flash (ZeroClipboard) and Flash-era plugins

Benefits: - Removes Flash-era dependencies (ZeroClipboard.swf, Jplayer.swf, jPlayer) - Eliminates ~300 dead files from the repository - No remaining references to either directory

Technical notes: - plugins/editors/tinymce/ and its manifest.json are unaffected - plugins/editors/ckeditor/ uses the current CKEditor 5, not the removed 4.x bundle

Updates all root-level and docs/ documentation to reflect changes made since the March 2026 snapshot: highlight.js integration, editor system migration, removal of legacy plugins, and the pluggable Editor architecture. Dates updated to April 2026.

Core changes:

1. README.md:
2. Remove Migration: 90% Complete badge (static metric)
3. Update Tech Stack: Editor class and pluggable plugins/editors/ system
4. Update Content Parsing: Parser class (not bare filterMarkdown)
5. Update project structure: add editor.php, parser.php entries
6. Remove docs/TEMPLATE_STATUS.md reference (file deleted)
7. Update plugins/ description to reflect current directory contents
8. CONTRIBUTING.md:
9. Add Content Parsers and Editors section with Parser and Editor API guidance
10. Remove MySQL/MariaDB version TODO (resolved by badge in README)
11. UPGRADING.md:
12. Add Content Editors section: Editor::getContent() / Editor::getCode() migration
13. Add Content Parsing section: Parser::filterContent() replaces filterMarkdown()
14. Fix storage/sitemap path reference
15. SECURITY.md:
16. Update storage paths for sitemap data
17. docs/TESTS.md:
18. Add ParserFixturesTest.php to Unit test list
19. docs/TEMPLATES.md:
20. Minor alignment with current runtime state

Benefits: - Documentation accurately reflects the active plugin stack and editor API - Contributors no longer see references to deleted functions or plugins - Parser and Editor migration paths are explicitly documented

Technical notes: - docs/TEMPLATE_STATUS.md was removed in the plugin cleanup commit - No new documentation files created; existing files updated in place