Чтение RSS каналов

changelog

Фильтр и поиск

Всего: 365 доступных коммитов | Отфильтровано: 365 коммитов | Страница: 1 / 37
Сегодня (06.03.2026)
Refactor: harden and normalize monitor admin module
Автор: Eduard Laas | Дата: 14:49 06.03.2026

Harden the admin monitor module output and refresh paths while bringing the file closer to the local SLAED coding rules. Also add repository text-format defaults so editors and Git keep UTF-8 and LF consistently.

Core changes:

  1. Monitor admin module (admin/modules/monitor.php):
  2. Harden request, server, and database diagnostic output before it reaches the admin template * Keep inline HTML escaping at the output boundary * Replace SHOW TABLE STATUS with an information_schema query

  3. Reduce refresh overhead and align the file with local style rules * Add short-lived caching for expensive monitor probes * Remove unnecessary Linux shell fallbacks and normalize comments, guards, and names

  4. Repository text settings (.editorconfig, .gitignore):
  5. Add shared UTF-8 and LF defaults for editor saves
  6. Stop ignoring tracked project meta files that must stay under version control

Benefits: - Improves admin-side XSS resistance for diagnostic values - Reduces monitor refresh cost on repeated polling - Aligns the module and repository text handling with project rules

Technical notes: - Existing monitor routes and template structure are preserved - Line ending policy is now enforced through repository metadata - Backward compatibility is preserved for the current admin workflow

Fix: Restore permanent gitmessage template
Автор: Eduard Laas | Дата: 11:58 06.03.2026

Restore .gitmessage as a persistent commit message template instead of a concrete commit message file. This keeps the Git workflow aligned with the current SLAED rules and prevents the template from being overwritten again.

Core changes:

  1. Git workflow template (.gitmessage):
  2. Restore the placeholder-based permanent commit template
  3. Remove the previous concrete commit content from the template file

Benefits: - Keeps commit preparation consistent across future tasks - Prevents accidental reuse of an old concrete commit message - Aligns repository workflow with the current SLAED Git rules

Technical notes: - No code behavior changes - No API or routing changes - Backward compatibility is unchanged

Refactor: Unify changelog core and modernize admin tools
Автор: Eduard Laas | Дата: 11:49 06.03.2026

Consolidate changelog loading, rendering, localization, and export behavior across public and admin code paths. Modernize monitor and editor admin modules to align them with the current SLAED routing and input rules.

Core changes:

  1. Changelog module (modules/changelog/*.php, templates/admin/basic-changelog*.html):
  2. Introduce shared changelog core logic in modules/changelog/common.php * Unify GitHub/local source loading, cache handling, pagination, and export helpers * Remove active GraphQL usage and count available commits from loaded data

  3. Refactor admin and public changelog handlers to use shared loaders and render helpers
  4. Localize admin changelog UI and refresh related module language files
  5. Admin tools (admin/modules/monitor.php, admin/modules/editor.php):
  6. Simplify monitor controller flow and centralize runtime snapshot handling * Reduce duplicated disk/runtime logic and remove external admin template dependency

  7. Refactor editor input handling to use shared helpers and SLAED raw input access
  8. Language and template alignment (language/*.php, templates/admin/*.html):
  9. Add missing monitor and changelog language constants across six languages
  10. Update admin templates to match the new changelog and monitor behavior

Benefits: - Better maintainability through shared changelog logic and reduced duplication - Cleaner admin behavior aligned with current SLAED rules for input and routing - More consistent localization and admin rendering across modules

Technical notes: - modules/changelog/common.php is a new shared module file - Commit counting now reflects available loaded/cached commits instead of GraphQL totals - Backward compatibility is preserved for existing changelog routes and admin operations

Вчера (05.03.2026)
Refactor admin tabs and streamline monitor dashboard
Автор: Eduard Laas | Дата: 22:47 05.03.2026
Feature: update monitor template and add htmx client asset
Автор: Eduard Laas | Дата: 18:07 05.03.2026

Adds the HTMX client library to admin assets and updates the monitor admin template markup. This commit groups the remaining UI-side changes into one atomic delivery for deployment.

Core changes:

  1. Monitor template (templates/admin/basic-monitor.html):
  2. Updated monitor admin layout and template blocks
  3. Improved partial rendering markup for monitor panels
  4. Frontend dependency (templates/admin/js/htmx.min.js):
  5. Added bundled HTMX minified script for admin monitor interactions

Benefits: - Enables template-driven interactive monitor updates - Keeps monitor frontend assets versioned in repository - Delivers remaining workspace changes as one deployable unit

Technical notes: - No backend PHP logic changes in this commit - No database/schema changes - Backward compatibility is preserved at template level

Refactor: align monitor admin module with SLAED skills baseline
Автор: Eduard Laas | Дата: 18:05 05.03.2026

Refactors monitor module internals to comply with SLAED security and refactor rules while preserving behavior. The update removes prohibited patterns and normalizes request/runtime handling in a way that is easier to audit.

Core changes:

  1. Navigation and signatures (admin/modules/monitor.php):
  2. Updated navi() to the SLAED admin signature baseline
  3. Added strict typing to getTooltipText()
  4. Input and runtime handling (admin/modules/monitor.php):
  5. Replaced direct $_SERVER and $_COOKIE usage with helper wrappers
  6. Added server/cookie accessor helpers for safer and centralized reads
  7. Safety and output hardening (admin/modules/monitor.php):
  8. Removed @ error suppression from file access paths
  9. Hardened tooltip attribute escaping and normalized concatenation style
  10. Removed in-function comment in catch block per project preamble

Benefits: - Better alignment with SLAED skills and system preamble - Improved auditability of request data access - Reduced risk from suppressed file operation errors

Technical notes: - No DB schema changes - No routing changes - Compatible with existing monitor template placeholders

На этой неделе (04.03.2026)
Fix: modernize monitor UI and unify size formatting filters
Автор: Eduard Laas | Дата: 22:12 04.03.2026

Implement UI and backend updates for System Monitor and align size formatting naming across the codebase. This improves dashboard readability, consistent styling behavior, and standardizes helper naming according to current SLAED conventions.

Core changes:

  1. Monitor module and core helpers (admin/modules/monitor.php, core/system.php):
  2. Reworked monitor metrics mapping and gauge placeholders for CPU/RAM/Disk. * Added RAM gauge dash binding and threshold-based color mapping. * Renamed size helper usage to filterSize(...) project-wide.

  3. Updated size filter implementation and naming consistency.
  4. Admin templates and presentation (templates/admin/basic-monitor.html):
  5. Refined top layout and moved Software panel to ROW 1.
  6. Expanded Traffic panel to full width and stabilized SVG stroke rendering. * Added vector-effect="non-scaling-stroke" for consistent chart line thickness. * Updated gauge and percentage colors via dynamic placeholders.

  7. Integrated Bootstrap Icons for panel titles and software rows.

Benefits: - Better visual hierarchy and readability in System Monitor. - Consistent size formatting API across modules. - More predictable chart rendering independent of container scaling.

Technical notes: - No database schema or API contract changes. - Backward compatibility preserved for runtime behavior; changes are UI/style and naming alignment.

Fix: stabilize monitor metrics and improve traffic rendering
Автор: Eduard Laas | Дата: 15:33 04.03.2026

Refines the System Monitor backend collectors and chart rendering so displayed runtime metrics are closer to actual host values across Windows and Linux environments. This reduces false readings and improves operator trust in admin diagnostics.

Core changes:

  1. Metrics collection hardening (admin/modules/monitor.php):
  2. Improved Windows memory and CPU detection flow with stronger fallbacks. * Added PowerShell CIM-based paths before legacy WMIC fallback. * Normalized counters and added safer numeric parsing for network values.

  3. Improved Linux disk I/O aggregation to avoid partition double counting.
  4. Monitor UI data and chart output (templates/admin/basic-monitor.html):
  5. Updated traffic chart SVG scaling behavior for stable rendering.
  6. Reduced traffic line stroke width for cleaner visual density.

Benefits: - More accurate monitoring output on modern Windows hosts. - Better cross-platform metric consistency and fewer misleading values. - Cleaner traffic graph readability in admin dashboard.

Technical notes: - No schema/storage changes. - No public API changes; admin monitor internals only. - Backward compatibility preserved for monitor page routes and placeholders.

Docs: Update project documentation and harden security
Автор: Eduard Laas | Дата: 14:10 04.03.2026

This commit audits and rectifies critical discrepancies across our project documentation (README, CONTRIBUTING, UPGRADING, PRINCIPLES, TESTS) aligning them with our current 6.3.x codebase. It also includes comprehensive security hardening configurations and minor syntax optimizations inside admin/modules/monitor.php and core/security.php based on recent audits.

Core changes:

  1. Project Documentation (README.md, CONTRIBUTING.md, UPGRADING.md, docs/):
  2. Rectified module counts and naming (26 modules, 'media' instead of 'gallery').
  3. Replaced outdated 'phpcs' check with 'php-cs-fixer' in contribution guidelines. * Ensures contributors use the correct static analysis tool.

  4. Standardized documentation to strictly refer to the 5 Core SLAED Principles (Fast, Stable, Effective, Productive, Secure).
  5. Added previously omitted testing suites (LanguageConstantsUsageTest.php, UnusedCodeAuditTest.php) to docs/TESTS.md.
  6. Uniformly enforced setRedirect() in code examples, removing obsolete header()+exit; legacy patterns.
  7. Codebase Security & Optimization (core/security.php, admin/modules/monitor.php):
  8. Strengthened input validation and regex application to avoid false-positives and potential regex injections.
  9. Eliminated redundant queries and unnecessary type-casts in monitor.php.
  10. Improved checkFiles array checks to mitigate potential TypeError deprecations in PHP 8.4+.
  11. Refined blocker configurations and logging bounds for Super Admin monitoring clarity.

Benefits: - Eliminates developer confusion by thoroughly ensuring alignment between official guidelines and actual PHP 8.4 codebase implementations. - Reinforces protection mechanisms against configuration corruption or user-input injections. - Minor efficiency gain by removing duplicate database server version queries inside monitoring logic.

Technical notes: - The documentation now precisely matches the codebase capabilities signifying ~85% modernization completeness. - Removed arbitrary references to obsolete .rules/ files that never existed.

На этой неделе (03.03.2026)
Perf: replace unset() with null assignment for qresult in getSqlQuery()
Автор: Eduard Laas | Дата: 15:07 03.03.2026

unset() on an object property removes the property entirely from the object, causing a property lookup overhead on next access. Assigning null keeps the property slot initialized and avoids re-allocation.

Core changes:

  1. Database::getSqlQuery() (core/classes/pdo.php):
  2. if (\$this->qresult) unset(\$this->qresult) → \$this->qresult = null

  3. Unconditional assignment removes the conditional branch overhead

Benefits: - Performance: avoids property re-declaration on each query cycle - Consistency: property remains defined on the object at all times - Maintainability: clearer intent (reset vs. remove)

Technical notes: - Functional behavior identical: qresult is falsy in both cases - Backward compatibility: no API changes

Всего: 365 на 37 страницах по 10 на каждой странице

Хотите опробовать SLAED CMS в действии?

Технологии

PHPMySQLHTML 5CSS 3jQueryjQuery UI

Контакты

  • D-49179, Deutschland
    Ostercappeln, Im Siek 6
  • +49 176 61966679

  • https://slaed.net
Идеи и предложения
Обратная связь