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

Voting results and the debug-stats panel used two parallel bar systems: a <meter>-based .sl-vote-meter with ~135 lines of vendor pseudo-element hacks, plus orphaned --sl-progress-* variables. Unify everything on a single gradient div component .sl-progress-line and drop the meter system.

Core changes:

1. Markup (lite + admin fragments):
2. voting-view, debug-stats: <meter> replaced by .sl-progress-line div bars
3. Styles (lite + admin base.css, theme.css):
4. Add .sl-progress-line / .sl-progress-1..5 gradient rules
5. Remove all .sl-vote-meter rules and --sl-vote-meter-* variables
6. Component is margin-neutral; spacing scoped to .sl-vote-list / .sl-vote-result
7. Lite bars thickened to 10px track / 8px fill, radius 3px; admin keeps 6/4/2

Benefits:

• One bar component instead of two; net fewer lines of CSS
• Consistent cross-browser rendering, restored gradient look

Technical notes:

• Threshold color (debug success/info/warn/danger) preserved via sl-progress-{N}
• Admin and lite themes remain independent

Array form fields must be read via the name[] key suffix; getVar() never supported a type='array' argument, so ~20 callers that passed it fell through to the scalar path where filter_input() returns false on an array, crashing with "count(): ... false given" (e.g. admin poll save).

Core changes:

1. Input reader (core/security.php):
2. Revert getVar() to detect arrays only by the key[] / key[n] syntax
3. Drop the unsupported 'array' type branch
4. Callers migrated to key[] (raw, indexes preserved):
5. voting/admin: body[], answer[] (keeps body<->answer alignment)
6. news/admin, shop/admin: associated[], id[]
7. media, media/admin: links[]
8. money, money/admin: intro[]
9. forum, pages/admin: id[]

Benefits:

• Fixes admin poll save and other multi-value form handlers
• Single canonical way to read arrays, matching existing key[] callers

Technical notes:

• Empty filter type returns the raw array (no element stripping)
• Behavior-preserving: previously these calls returned false (broken)

Document SLAED's existing extension mechanisms and a safe direction for an admin-managed plugin layer based on the editor manifest/driver pattern.

Core changes:

1. Plugin analysis (docs/PLUGINS.md):
2. Survey current mechanisms (modules, editor plugins, captcha provider, vendored libs)
3. Recommend generalizing the manifest + driver + registry pattern
4. Propose a managing (not installing) admin page; warn against remote PHP install

Benefits:

• Shared reference for unifying SLAED's extension points

Technical notes:

• Documentation only; no code change

The admin theme draws its own checkbox glyph via a background-image, which stacked on top of the ALTCHA widget's own SVG check mark (rendered in light DOM), so the verified captcha showed two check marks.

Core changes:

1. Admin theme (templates/admin/assets/css/theme.css):

2. Suppress the admin checkbox background glyph on .altcha-checkbox inputs (:checked / :indeterminate), leaving only ALTCHA's own check mark

Benefits:

• Single, correct check mark in the admin login captcha

Technical notes:

• CSS only; scoped to .sl-admin-shell .altcha-checkbox; the lite theme was unaffected

Replace the terse "Verified" label with a clear confirmation sentence in the captcha verified state, across all shipped languages.

Core changes:

1. Captcha strings (lang/*.php):

2. _CAPTCHA_VERIFIED now reads as a full success sentence

   • ru: "Проверка успешно завершена!"
   • de/en/fr/pl/uk: equivalent wording, kept in sync

Benefits:

• Clearer feedback to the user right after solving the captcha

Technical notes:

• Text only; no behavior change; mapped to the ALTCHA i18n key "verified"