The extension field of the dashboard answered one and the same string whether it had found every module of the directory loaded or had never been able to read that directory at all, so an installation whose extension_dir lies outside open_basedir was told that nothing was missing. The same commit writes down the plan for the journals and for the data around them.

Core changes:

1. Three states where there were two (admin/modules/monitor.php):

2. Whether the module directory can be read at all is decided before it is walked

   • extension_dir is not set, lies outside open_basedir, or is not a readable directory
   • The reason travels with the verdict and names both paths, so the answer can be acted on
3. None now means every module on disk is loaded, and N/A means the directory was never read

4. The block follows the rules of the project again: names without underscores, no single line if and else in braces, no blank line inside the body

5. A plan for the journals and the data around them (docs/PRIVATE-DATA-2026.md):

6. Batch 1: no secret reaches a journal

   • The login report stops printing the password it is handed on a failed attempt
   • The request dump passes through the masking rule Logger already owns, and records the key

names of the session and the cookies instead of their content

• Batch 2: the installation proves its private directories are private

  • A marker fetched over its own address and judged by the body, because a status code decides

nothing where errors are mapped onto a page

• Three verdicts and never two: closed, open, and a transport that could not run

• Batch 3: a server configuration in the delivery, held to the tree by a test that enumerates the directories declaring themselves private and demands the fragment cover each of them

• Batch 4: the runtime tree out of the document root, as the migration of a major release

• Batch 5: one prefix per meaning in the journal names

  • error_ is what the system could not do, log_ is what happened
  • The file journal splits into log_file.log for every operation and error_file.log for the

error level alone, hack.log becomes log_hack.log and warn.log becomes log_warn.log

• The routing follows the levels that are already set, so no record is classified twice

Benefits:

• A field of the dashboard stops answering a question nobody asked it

• The decisions taken about the journals are written down with their reasons instead of living in a conversation

Technical notes:

• No behaviour of the site changes: the monitor reports differently and the document adds no code

• The plan names functions, files and constants rather than line numbers, so it survives the next edit of the files it points at

• The label map of the security section keeps the retired keys, so journals already on disk do not lose their names when batch 5 lands

The upload service gains one structural validator per format, so a PHP build compiled without Fileinfo publishes every one of the 21 allowed types by walking the container instead of trusting a name. The same commit carries the word limit of comments, private messages and the forum, where zero now bounds no word instead of refusing every body.

Core changes:

1. Content validation without Fileinfo (core/classes/upload.php):

2. The magic database stays the first reader and the fallback answers only where it cannot

   • Bounded fopen, fread and fseek, so a file of any size is judged without being held in memory
   • Fifteen validators: image type marker, two consecutive MPEG frames, RIFF chunk chain, FLAC

metadata blocks, Ogg page checksum and codec, ISO BMFF brands with the track handler that
separates m4a from mp4, EBML doctype, PDF header and trailer, zip central directory, RAR block
chains, gzip stream against its own CRC and length, 7z start header, tar header checksums

• A type the database did name is answered unchanged, so a conflict with the extension is refused

rather than asked a second time

• The check order is fixed: missing, size, transfer and extension answer before anything is read

• getTypeReader() becomes protected, which is the seam a test closes while every other extension of the machine stays available

• One validator for both flows (core/classes/upload.php):
• getFileMime() takes the verified extension and answers the canonical type of the format
• addRemoteFile() no longer refuses a whole build over the type reader; cURL keeps its own check
• A missing capability told apart from a refused file (core/system.php, modules, lang):
• unsupported gets the neutral _ERROR_SERV text in all six locales
• The three inline mappings of the modules now read the one getUploadFailText() resolver
• error_file.log distinguishes fileinfo_missing, fileinfo_init_failed, decoder_missing, curl_missing
• Word limit of zero (core/classes/comment.php, core/classes/privat.php, modules/forum):
• Zero bounds no word instead of refusing every body, and the longest word is counted in characters
• The forum setting becomes a number field with its hint instead of a yes or no switch
• Tests (tests/Support/upload_probe.php, tests/Unit/UploadFallbackTest.php):
• Every non-image fixture is structurally complete now, checksums included

• New scenarios: each format without a magic database, the matrix of one body under every foreign extension, corrupted and polyglot bodies, the refusals that come first, and the remote half

Benefits:

• A production build without Fileinfo publishes uploads again without weakening content validation
• A disguised, truncated or corrupted file is refused by the structure of the format it claims
• One mapping explains a refused upload on every screen

Technical notes:

• Routes, JSON, the eight key result shape and the database are unchanged
• ext-fileinfo, ext-zip and ext-zlib move from require to suggest in composer.json
• The suite passes on a build with the extension and on one without it

Every string this page shows stands in a chip, a shelf note, a card or a counter, and never inside a sentence, so each one begins with a capital and drops the words its box cannot carry. The forward prefix stops being an untranslated abbreviation and becomes the noun each locale really uses, the way the reply prefix already did.

Core changes:

1. The chips of the compose header (lang/*.php):
2. _PRWAIT reads «Интервал 60 сек.» where it read «интервал между отправками 60 секунд»

3. _PRLIMTO and _PRLIMSUB name the field and the bound and nothing else

   • «Имя, до 25 символов» and «Заголовок, до 100 символов»
   • all three now stand on one line at 1240 and 800 and on two at 390, where they wrapped
4. The recipient card (lang/*.php):

5. _PRBOXFULL, _PRBOXNEAR and _PRBOXROOM drop «получателя»

   • the name of the account stands one line above them in the same card
6. The forward prefix (lang/*.php):

7. _PRFWD was the untranslated Fwd in all six locales

   • it becomes «Пересылка», Forwarded, Weitergeleitet, Transfert, Przekazane, «Пересилання»
   • a forwarded subject now reads «Пересылка: …» the way a reply reads «Ответ: …»
8. Capitals where a string stands alone (lang/*.php):

9. _PRFREE, _PRSHOWN and _PRNOLIMIT, plus the Polish _PRFOCUSN

   • an outbox holding nothing prints _PRNOLIMIT with no counter before it, so it starts a line
   • the counter prints _PRSHOWN alone whenever no search is running

Benefits:

• a chip says what it means without being cut or wrapped
• nothing in the interface is left in an abbreviation only one language reads

Technical notes:

• values only: no constant is added, renamed or retired, and every placeholder is preserved
• all six locales carry the same wording in the same change
• docs/PRIVATE-MESSAGES-2026.md records the pass and the widths it was measured at

The private message page no longer redraws a whole tab for every action. A reader opens a message beside its list instead of in place of it, narrows the mailbox from a toolbar above it, and reads the quota off a ring on each shelf rather than off an alert that fired from half capacity.

Core changes:

1. Private message subsystem (core/classes/privat.php):

2. The list answers a selection instead of a whole mailbox

   • getPickWhere() lays the state, period and search conditions over the box predicate
   • one placeholder per column and a declared ESCAPE, because prepares are native here
   • the period binds a number of days, so the boundary is drawn by the server that wrote the row
3. getBoxFacets() answers every chip number in one aggregate row
4. getSortOrder() picks from four fixed shapes, each closing on a unique tie-breaker on the id
5. getUnreadBoxCount(), getBoxLimit() and getBoxFill() answer the shelves and their rings
6. The list row carries a snippet the server cuts, and getMessageView() answers the same cut
7. Routes and adapters (core/user.php, modules/account/index.php):
8. privat() loses the four htmx tabs and reads id, typ and uname
9. getPrivateMessageView() answers one column: a mailbox, a message or the empty pane
10. setPrivateMessageRead() answers the reading pane, with the row and the counters out of band
11. getPrivatPick() reads the selection under fixed names and reduces it to fixed values
12. getPrivatRowData(), getPrivatShelves() and getPrivatBadges() own the row and the counters
13. The page number leaves cid and travels as pnum, so cid keeps its two meanings and gains no third
14. Templates (templates/lite):
15. partials/privat-page.html, privat-list.html, privat-view.html and fragments/privat-row.html
16. One swap boundary each: the shell, the left column, the reading pane and a single row
17. The shelf strip, the toolbar, the filter chips and the shared sl-knob ring
18. Client behaviour (plugins/system/slaed.js):
19. The pane switch and the back button of the narrow layout
20. The reply form filled through the editor API from a hidden carrier textarea
21. The filter chips, each group holding its value in one hidden field

Benefits:

• Opening a message keeps the scroll position, the checkbox selection and the editor instance
• The list, the filtered count and the pager come out of one predicate set inside one answer
• The shelves and the chip facets answer the mailbox and stay independent of the toolbar
• One tone ladder serves the quota rings, the server gauges and the debug panel

Technical notes:

• No schema change and no new route; every state-changing route stays behind POST and the token
• Row and reading-pane actions send no body at all, so the selection form cannot override them
• Every new language constant is present in all six locales
• The search stays a scan of one mailbox: EXPLAIN answers ref on in_box and never a table scan
• docs/PRIVATE-MESSAGES-2026.md records which batches landed and what was measured
• docs/UPLOAD-FILEINFO-PLAN-2026.md is an unrelated plan document carried in the same tree

Adds design prototypes for the account private-message page: eight distinct approaches, the variant selected from them, and three labs that settle the quota indicator and the filter toolbar. No runtime code, template or stylesheet is touched; every page is a self-contained artefact under demo/.

Core changes:

1. Eight approaches (private-messages-v1-mailbox.html ... v8-flow.html):

2. One page per approach: mailbox, split view, dense admin register, cards, messenger, minimal, high-volume and an experimental flow concept

3. Each page covers inbox, outbox, unread, selected message, sender, subject, date, status, open/reply/delete/mark actions, search, filtering, paging, empty state and a mobile rendering

   • Mobile layouts run on @container, so the phone frames are the real narrow

rendering rather than a picture

• The message field mounts the actual Toast UI editor from

plugins/editors/toastui instead of a placeholder textarea

1. Chosen layout (private-messages-final-2026.html):
2. Two-pane base: the list keeps its place while a message opens beside it

3. Folder tiles carry an SVG quota ring in place of the text alert; the arc and the icon share one tone

   • Folders without a quota, the outbox and compose, draw a solid ring instead
   • pathLength="100" normalises the arc, so one percent is all a template needs

4. The filter strip became a control: chips toggle, so a cleared filter can be restored, and read/unread exclude each other

5. Reading toolbar keeps message actions together and moves navigation aside

6. Decision labs (private-messages-quota-lab.html, quota-halo.html, toolbar-lab.html):

7. Thirteen quota indicators, each in three states, all built from mechanics the theme already owns

8. The refined ring with its thickness, size and cap alternatives
9. Six filter-toolbar layouts with their trade-offs
10. Index (private-messages-index.html):

11. Description, benefits and drawbacks of every variant, a comparison table and links to all pages

12. Records what the live page revealed and the contract each block would need

Benefits:

• The layout decision rests on the running site rather than on assumptions

• Reuse over invention: tables, chips, dial, pager, bulk bar, alerts, progress lines and rings all come from templates/lite

• Every page states what the backend must supply, so integration can start from a written contract instead of a redrawing round

Technical notes:

• Demo only: no PHP, template or theme file is modified

• Extra CSS lives inside each page under its own prefix and never reaches the theme

• Pages load repository assets only; no CDN and no new dependency

• The chip set carries no attachment filter: _privat has no such column and a LIKE over the message body would scan the whole table

• sl-knob exists only in templates/admin; using it on the site would require moving that block into templates/lite first

• Backward compatible: nothing outside demo/ is affected