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

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

Всего: 896 Доступных коммитов | Отфильтровано: 896 Коммиты | Страница: 1 / 90
Вчера (18.06.2026)
Docs: document Nginx error_page setup in editor help
Автор: Eduard Laas | Дата: 19:12 18.06.2026

The Apache rules section of the editor help now notes that Nginx and IIS do not read .htaccess and shows the error_page directive needed to route HTTP errors to the styled CMS error page.

Feature: universal styled error/message page for both themes
Автор: Eduard Laas | Дата: 19:12 18.06.2026

setExit() now renders a single styled card (logo, gradient divider, message, home/search) for every error and notice, in both the lite and admin themes. Assets resolve through an absolute <base href> built from homeurl so the page keeps its styling even when served from a deep URL, and all <head> tags are emitted via fragments (head-base, head-meta, meta-refresh) instead of inline HTML. The login divider and the message divider share a single --sl-line-gradient token. access.php becomes a thin guard, and _ERROR404 is reworded into a neutral, universal _ERROR_PAGE across all six locales.

Fix: preserve Markdown on admin info-doc save and scope doc styling
Автор: Eduard Laas | Дата: 19:12 18.06.2026

Saving an info/help doc ran the Markdown source through filterHtml(), which (for the CodeMirror branch) applied nl2br + htmlspecialchars + $/quote escaping and corrupted the file on the first save. Info docs are rendered in trusted mode (filterContent safe=false), so store the raw Markdown with normalized LF line endings instead. Wrap the rendered doc in a scoped .sl-markdown container (via the generic div partial) and add spacing rules so the help pages no longer render cramped.

Chore: remove unused getAdminInfo info endpoint
Автор: Eduard Laas | Дата: 19:11 18.06.2026

getAdminInfo() was an AJAX duplicate of setTplAdminInfoPage() reachable only via the index.php dispatch case 'getAdminInfo', which nothing in the UI ever triggered. Drop the function and its dispatch case.

Refactor: rename admin help-tab label _INFO to _DOCS
Автор: Eduard Laas | Дата: 19:11 18.06.2026

The info/help tab in every admin section reused the generic _INFO label ('Информация'). Introduce a dedicated _DOCS constant ('Справка' / 'Documentation') in all six locales and switch the tab bars to it, leaving _INFO for the generic tooltip/nav usages that genuinely mean 'information'.

Style: align admin form validation and clean class hooks
Автор: Eduard Laas | Дата: 12:56 18.06.2026

Bring admin inputs to the same modern validation UX as lite and remove duplicate or ambiguous class hooks, keeping the admin palette.

Core changes:

  1. Modern validation (assets/css/base.css):
  2. Replace required:valid/:invalid text coloring with :user-invalid/:user-valid border and ring
  3. Add danger and success focus tokens
  4. Wrap the over-specific input :hover exclusions in :where() so focus and validation win
  5. Class consolidation (assets/css/theme.css, fragments, partials):
  6. Rename the .sl-field width utility to .sl-field-auto so it no longer clashes with the lite .sl-field
  7. Reduce the duplicated .sl-changelog-filter-field input rule to width:100%
  8. Toggle ids sl_block_ become sl-block-; drop the dead --sl-shadow-input fallback

Benefits:

  • Consistent modern validation across both themes
  • Unambiguous class names and less duplication

Technical notes:

  • :user-invalid and :where() target modern browsers
  • Visual behavior preserved; neutral value text
Style: modernize and consolidate lite form controls
Автор: Eduard Laas | Дата: 12:56 18.06.2026

Give the lite theme one field look, modern validation, a Yes/No switch and custom checkbox aligned with admin, and remove legacy class hooks.

Core changes:

  1. Unified field styling (assets/css/base.css, assets/css/theme.css):
  2. Canonical .sl-field for input/textarea/select with focus ring and disabled state
  3. Field height aligned to the 30px buttons; neutral value text
  4. :user-invalid/:user-valid validation as border and ring, only after interaction
  5. Form field, checkbox and switch design tokens
  6. Controls aligned with admin (assets/css/theme.css, fragments):
  7. Custom checkbox with brand check mark
  8. Yes/No segmented switch (.sl-radio-switch) in the lite green palette
  9. Class consolidation:
  10. Tabs hook div[id^="sl_tabs_"] becomes .sl-tabs plus data-sl-tabs with a hyphenated id (assets/js/tabs.js, fragments/navi-tabs-wrap.html)
  11. Toggle ids sl_block_ become sl-block- (partials/block-sidebar.html)
  12. Tokenize duplicate and seasonal colors; drop the dead --sl-shadow-input fallback

Benefits:

  • One field class and a consistent modern look across lite forms
  • No underscore class or id hooks left
  • Easier theming through tokens

Technical notes:

  • :user-invalid, :where() and :has() target modern browsers
  • No markup behavior change beyond class and id renames
Refactor: centralize input control type in the template layer
Автор: Eduard Laas | Дата: 12:55 18.06.2026

Derive the input type from the field name in one shared place so admin and lite stop repeating per-call-site itype, and semantically equal fields can no longer drift apart.

Core changes:

  1. Input-type derivation (core/classes/template.php):
  2. Add getInputType() mapping field names to email/url/password
  3. Apply it in getHtmlFrag() for the input fragment
  4. Explicit itype always overrides the derived default
  5. Redundant itype sweep (admin/index.php, modules/*):
  6. Drop now-derived itype for mail/url/password fields across modules
  7. Set email/url types for guest author and site fields (files, links, auto_links)
  8. Keep special cases explicit (whois domain/host/dc, changelog ghtoken)

Benefits:

  • Single source of truth for input type across both themes
  • Native :user-invalid validation now works on email/url everywhere
  • Less duplication and no per-module type drift

Technical notes:

  • No database or schema changes
  • Behavior preserved; only the default type derivation moved to the core
Эта неделя (17.06.2026)
Chore: relicense from GPL-3.0 to MIT
Автор: Eduard Laas | Дата: 14:41 17.06.2026

Relicense SLAED CMS from GPL-3.0 to MIT and remove the runtime license lock. The project author relicenses their own work, so attribution enforcement is dropped and the obfuscated copyright config is retired.

Core changes:

  1. License text and metadata (LICENSE, composer.json, package.json, README.md):
  2. Replace the GPL-3.0 text with the MIT license and update license fields/badges
  3. Source headers (~396 .php, .htaccess, setup/sql/.sql):
  4. Change "# License: GNU GPL 3" to "# License: MIT"
  5. Normalize the copyright line to "# 2005 - 2026 SLAED"
  6. Runtime license lock removal (core/system.php, setup/index.php):
  7. Remove the _NO_LICENSE admin and setup lock checks
  8. Drop the lic_h/lic_f config keys and their forced rewrite on config save
  9. Replace the four footer builders with a single getLicenseHtml()
  10. Decouple the legacy md5 password salt into a frozen PASS_SALT constant
  11. Remove the now-dead _NO_LICENSE constant from all locale files
  12. Documentation (README, CONTRIBUTING, SECURITY, UPGRADING, CODE_OF_CONDUCT, .rules/architecture.md):
  13. Replace GPL references with MIT

Technical notes:

  • Legacy md5 logins keep working through the frozen PASS_SALT value
  • Historical news seed data in setup/sql/insert.sql is left intact on purpose
  • Third-party code under plugins and vendor is not touched
Style: align and fit the footer license line
Автор: Eduard Laas | Дата: 14:41 17.06.2026

Adjust footer CSS so the MIT license line reads cleanly after the relicense changed the text length.

Core changes:

  1. Site footer (templates/lite/assets/css/theme.css):
  2. Center .sl-copyright/.sl-license and balance the wrapped lines
  3. Admin login footer (templates/admin/assets/css/theme.css):
  4. Reduce .sl-admin-login-copyright font-size so the line fits one row on desktop and narrow widths

Benefits:

  • Footer license stays readable and centered without clipping

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

1 2 3 4 5 6 7 8 9 10 90

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

Идеи и предложения
Обратная связь