Reviewed & tested by the community
Project:
Drupal core
Version:
11.x-dev
Component:
base system
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 May 2026 at 21:44 UTC
Updated:
6 May 2026 at 15:21 UTC
Jump to comment: Most recent
Comments
Comment #2
godotislateComment #4
godotislateMR https://git.drupalcode.org/project/drupal/-/merge_requests/15681
MR jobs for PHP 8.3 with PostgreSQL, mysqli, and SQLite all green
https://git.drupalcode.org/project/drupal/-/pipelines/813515
Last 11.x commit with test failures:
https://git.drupalcode.org/project/drupal/-/pipelines/813348
Comment #5
godotislateOne question is whether the readonly should also be removed in
main, but I don't think that's a BC break.Comment #6
nicxvan commentedThey aren't in a release yet afaict, should be safe to change on main.
Comment #7
godotislateOh, sorry, I meant that if we leave main with
readonly, then a site going from 11.4 to 12.0 could hit issues if there are subclasses that redeclare the same property withoutreadonly.Comment #8
catchI think the readonly is OK on main - properties on form controllers are supposed to be @internal.
Comment #9
godotislateI wonder if we should create an issue to update the 11.3 dump (or make a new one) with mysqli installed, if there isn't already one.
Comment #10
catchYes I think that's worth doing, I thought we had an issue but can't find it right now.
Comment #11
godotislateOpened #3588702: Enabled mysqli in test 11.3 dump.
Comment #12
godotislate#3588702: Install mysqli in test 11.3 database fixture is ready for review. It might make sense to get that in first so we don't need to backport the mysqli fixture to 11.x here.