PHP digest — 19 October 2026
A quiet Monday with four developments: the End PEAR endorsement poll closed unanimously, a vote was announced for the
Filter enums RFC, a Symfony 8.2 feature post, and two edits to the Uri\QueryParams RFC.
End PEAR endorsement poll closes 40–0–0
The poll on the End PEAR Project Endorsement RFC was scheduled to close
at 13:15 UTC. At about 16:05 UTC the page showed "Final result: 40 / 0 / 0" (Yes / No / Abstain) and "This poll has been
closed"; the RFC needs 2/3 Yes on its single question, "Stop endorsing PEAR?". The page header still says Voting, the
official RFC index still lists it as voting, and no result announcement had reached the internals feed, so this digest
does not yet call it accepted. The RFC proposes a static archive of pear.php.net (browsable until 2027-12-31), no longer
bundling the PEAR installer from PHP 8.7, and removing PEAR references from PHP websites. None of this is implemented;
the related php-src PR #20124 was an unmerged draft when last checked on
6 October. See the
RFC page.
Filter enums RFC: vote announced, not yet open
At 10:03 UTC the author of the Filter\Filter and Filter\Flag enums RFC
posted an intent-to-vote message saying voting "will start on October 19, 2026",
under the RFC's former title "Invalid Filter Options". At about 16:05 UTC the page still read Under Discussion, last
modified 9 October, with an unopened 0/0/0 widget for one 2/3 question; no closing date has been published. The proposal
adds int-backed enums that filter_var() and related functions would accept alongside the existing FILTER_* constants
(proposed PHP 8.7). The objection that combining flags through ->value bitmasks defeats the enums' type safety, raised
on 9 October, is not addressed on the page. See the RFC page.
Symfony 8.2: trans_html filter and HtmlTranslator for HTML in translations
The Symfony blog describes a trans_html Twig
filter and an HtmlTranslator class in the Translation component, added by
PR #66690 (merged into the 8.2 branch on 13 October; 8.2 is not
released). The post explains why it was added: translated messages that contain HTML are often printed with |raw. That
hardcodes URLs in translation files, renders whatever HTML translators wrote, and stops message parameters from being
escaped, which can cause XSS when a parameter holds user input.
With the new filter, translations contain only attribute-less pseudo-tags such as <signin_link>…</signin_link>. The
template maps each pseudo-tag to an element given as data (tag name and attributes), or to a list of elements to nest.
According to the post and the PR, the message text, parameters, attribute values and undeclared tags are escaped, a message
with unbalanced tags is escaped as a whole, and script/style are refused. The output needs no |raw and the filter
also accepts t() messages. HtmlTranslator::trans() provides the same in PHP, for example for HTML emails. These are
the authors' descriptions; this digest has not tested the escaping.
Uri\QueryParams RFC: list() and parseWhatWg() renamed
The wiki change feed shows two edits to the query parameters RFC, at 07:58 and
13:30 UTC, with no new internals message. The page now declares toList() instead of list() and
parseWhatWgUrlSearchParams() instead of parseWhatWg(), two of the changes the author
announced on 16 October. Its backward-compatibility section says the new
classes could clash with userland symbols in the Uri namespace. The other announced changes are not on the page: it
still has $maxQueryStringLength, mixed values in append()/set() and a single sort(), and still describes
tolerant parsing. The header still reads version 1.0, Under Discussion, with placeholder vote dates. No vote has been
announced. See the RFC page.
Coverage
Collections ran at 10:01 and 16:01 UTC. Both times the 32 due feed, release and index sources were collected
successfully; the 25 daily package, adoption, support-window and advisory sources were not due and keep their 22:01 UTC
data from 18 October. health --fail-stale reports all 57 sources ok and none stale. Since the
18 October edition the new collected records are the Symfony post, the two RFC page edits, two internals
messages (132879 above and 132880, a karma request to publish a "Scope" RFC on per-request superglobals, timezone and
locale for long-running PHP; its draft is not on the PHP wiki yet), a SymfonyCon Warsaw talk debrief, a freek.dev post on
retries, and a Laravel News article on DB::olap() added in Laravel 13.36 (PR #61932; the release was
covered on 14 October). The official RFC index still has 952 entries and the same three voting RFCs.