The font size of the placeholder label is large and breaks the UI.
1. Go on /admin/config/user-interface/navigation-block page
2. Uncheck the checkbox "Show content preview"
3. See the Layout builder region in the sidebar
4. Font size is breaking the UI.
Before
After: 
When returning a list of entities that are not the same, or a list of nodes with different content-types, if the "include" parameters is used, it checks for the first entity if this field can be included and if not possible, it raises an error with message:
title: "Bad Request",
status: "400",
detail: "`field_brighcove_video` is not a valid relationship field name. Possible values: node_type, uid, field_author, field_content, field_entity, field_main_publication_channel, field_other_publication_channel, field_section, field_series, field_source, field_team, field_teaser, field_topics, field_topic_entity.",
An example of module that uses JSON:API Resources is JSON:API Search API, which makes a lot of sense to return node within different content types.
Try getting multiple type of data in a single JSON API with include parameters having fields that are not common between different entity types you are trying to fetch.
My suggestion is to receive the resource identifier as part of include path and check that before include it, something like ?include=node--video.field_brighcove_video.
When using textfield set to Unlimited (or more than one) values I cannot changed the field size in Manage Form Display. Changed from 60 to any size more or less does nothing to the field.
Add a text field (any type) to any content and set the allowed values to anything other than one (1). Go to Manage Form Display and change the field size to any number and you'll see that it has no affect on the field.
I may have a solution, but I'm not completely convinced this is a true bug or something causing it on my end, and I don't know if the solution is sound. However, when I remove this CSS from core/theme/Claro/css/components/tables.css everything works fine and doesn't seem to have a negative impact. It doesn't even affect Paragraphs which is table based with these same CSS elements below.
Line: 214
Delete: td > .form-item > .form-element,
<del>td > .form-item > .form-element,</del>
td > .ajax-new-content > .form-item > .form-element,
td > .form-item > .claro-autocomplete,
td > .form-item > .claro-autocomplete > .form-element,
td > .ajax-new-content > .form-item > .claro-autocomplete,
td > .ajax-new-content > .form-item > .claro-autocomplete > .form-element {
width: 100%;
}
The solution I'm temporarily using is my own custom CSS below. With this the fields can be resized normally.
td > .form-item > .form-element {
width: auto;
}
None
None
None
None
None
PHP 8.4 will be released after Drupal 11, meaning we won't be able to use new features until we drop support for PHP 8.3. Fortunately symfony provides polyfills for many of these functions.
Add symfony/polyfill-php84. Modernize some areas of core to use array_find, array_all, array_any and other related functions. \Drupal\Component\Assertion\Inspector is a good place to start because it has many related functions and has good unit test coverage
using Drupal 11/10.3 standard profile.
enable Navigation module
with your browser, disable Javascript. make window less than 500px.
notice 'a bar at top' and bottom 'Expand sidebar'. this does nothing.
Also include 'navigation logo' in this area and breakpoint. As it serves are landmark for users and link to get into 'administration' when nojs and in this breakpoint.
- reminder: navigation has an template/svg.logo.twig -- Expand around with the custom logo use (with parent/wrapping link) then return that into the layout/navigation.html.twig so that it can be reused here.
choices:
- should this link to go /admin/index. (currently goes LOGO goes to Frontpage.
- should the logo link to 'return to site' type functionality. ie 'admin/index'->front->user_setting->return-to-side/(last known page?)
- should we add a setting for user to set their choice. default/none will be (front or admin/index).
enhance JS degrade of Navigation 'bar at top/mobile trigger'
Originally submitted on Github
The admin UI theme is being redesigned and Contextual links need to be integrated with the new design system.
Specs to follow for the contextual link icon: https://www.figma.com/file/OqWgzAluHtsOd5uwm1lubFeH/Drupal-Design-system...
The contextual links should not be styled as they are currently shown in the figma link. Instead, for consistency, the styling should match the existing dropbutton tray styling.
/recipes/watercress-soup.SDC is part of core now, so we can migrate the existing code to take advantage of SDC.
Move the component Toolbar button into its own SDC.
None
Hello, sorry for my English langage.
Context :
Site : https://aacm-france.fr
Host: PlanetHoster
CSV /Drupal version installed D10.3.0 managed with composer
Modules :
- drupal/ctools:^4.0
- drupal/imce:^3.0
- drupal/colorbox:^2.0
- drupal/media_gallery:^2.1
- drupal/admin_toolbar:^3.4
- drupal/vapn:^3.0@alpha
- drupal/ckeditor_font:^2.0@beta
PHP : 8.2.5
Database: 10.5.21-MariaDB
Bug: since update D10.2.7 to D10.3.0
Bug description: Modified display for creating or modifying an article, page or gallery with disappearance of areas of the writing body or summary (screenshots 1 -2 -3 ). In some cases semi-possible with simple HTML (screenshots 4 -5)
I tried to recreate the base of the site (core + modules + theme) several times directly with D10.3.0 same problem for each try.
In the reports: recent log messages: very many messages system. (screenshots 6 as 7 -8 -9).
Searches in the Drupal bug report: Issues for Drupal core: I couldn't find anything that resembled my problem.
Question: I don't understand why no one has the same problem. Is there a solution that I missed?
I would like to use a Text (formatted) field to create a "Description" field appropriate for an og:description meta tag, since we typically want to limit those to 100-300 characters max, and also want it to allow HTML tags since it could be used for display. It is not possible to use a textarea/CKEditor widget for these fields without https://www.drupal.org/project/textarea_widget_for_text
Allow the use of the "Text area (multiple rows)" widget
The new widget is available in the "Manage Display" form.
None
None
Since updating to Drupal 8.3, I am seeing the following messages in the (PHP) error_log file on my hosting provider...
[04-Jul-2024 05:33:22 UTC] PHP Warning: Invalid "output_buffering" setting. Invalid quantity "Off": no valid leading digits, interpreting as "0" for backwards compatibility in Unknown on line 0
[04-Jul-2024 05:33:22 UTC] PHP Deprecated: PHP Request Shutdown: assert.active INI setting is deprecated in Unknown on line 0
[04-Jul-2024 05:33:50 UTC] PHP Warning: Invalid "output_buffering" setting. Invalid quantity "Off": no valid leading digits, interpreting as "0" for backwards compatibility in Unknown on line 0
[04-Jul-2024 05:33:50 UTC] PHP Deprecated: PHP Request Shutdown: assert.active INI setting is deprecated in Unknown on line 0
[04-Jul-2024 05:33:50 UTC] PHP Warning: Invalid "output_buffering" setting. Invalid quantity "Off": no valid leading digits, interpreting as "0" for backwards compatibility in Unknown on line 0
[04-Jul-2024 05:33:50 UTC] PHP Deprecated: PHP Request Shutdown: assert.active INI setting is deprecated in Unknown on line 0
[04-Jul-2024 05:33:57 UTC] PHP Warning: Invalid "output_buffering" setting. Invalid quantity "Off": no valid leading digits, interpreting as "0" for backwards compatibility in Unknown on line 0
[04-Jul-2024 05:33:57 UTC] PHP Deprecated: PHP Request Shutdown: assert.active INI setting is deprecated in Unknown on line 0
[04-Jul-2024 05:37:15 UTC] PHP Warning: Invalid "output_buffering" setting. Invalid quantity "Off": no valid leading digits, interpreting as "0" for backwards compatibility in Unknown on line 0
[04-Jul-2024 05:37:15 UTC] PHP Deprecated: PHP Request Shutdown: assert.active INI setting is deprecated in Unknown on line 0
[04-Jul-2024 05:37:26 UTC] PHP Warning: Invalid "output_buffering" setting. Invalid quantity "Off": no valid leading digits, interpreting as "0" for backwards compatibility in Unknown on line 0
[04-Jul-2024 05:37:26 UTC] PHP Deprecated: PHP Request Shutdown: assert.active INI setting is deprecated in Unknown on line 0
[04-Jul-2024 05:37:34 UTC] PHP Warning: Invalid "output_buffering" setting. Invalid quantity "Off": no valid leading digits, interpreting as "0" for backwards compatibility in Unknown on line 0
[04-Jul-2024 05:37:34 UTC] PHP Deprecated: PHP Request Shutdown: assert.active INI setting is deprecated in Unknown on line 0
[04-Jul-2024 05:37:36 UTC] PHP Warning: Invalid "output_buffering" setting. Invalid quantity "Off": no valid leading digits, interpreting as "0" for backwards compatibility in Unknown on line 0
[04-Jul-2024 05:37:36 UTC] PHP Deprecated: PHP Request Shutdown: assert.active INI setting is deprecated in Unknown on line 0
As a result of this (I think, given that it says 'PHP Request Shutdown') I cannot any longer get to the Modules page (http://drupal10.local/admin/modules) and see a 500 error.
My settings.php and my settings.local.php have been a round a while, is there something that I need to change there that relates to assertions?
Oddly, I CAN get to the Modules page on my local (Windows) development version which is allegedly using exactly the same version of Drupal (10.3) and PHP 8.3.x
Thank you
user.mail is fully validatable
./vendor/bin/drush config:inspect --filter-keys=user.mail --detail --list-constraints --fields=key,validatability,constraints
➜ 🤖 Analyzing…
---------------------------------------------------- ------------- ---------------------------------------------------------
Key Validatable Validation constraints
---------------------------------------------------- ------------- ---------------------------------------------------------
user.mail 100% ValidKeys: '<infer>'
LangcodeRequiredIfTranslatableValues: null
user.mail: Validatable ValidKeys: '<infer>'
LangcodeRequiredIfTranslatableValues: null
user.mail:_core Validatable ValidKeys:
- default_config_hash
user.mail:_core.default_config_hash Validatable NotNull: { }
Regex: '/^[a-zA-Z0-9\-_]+$/'
Length: 43
↣ PrimitiveType: { }
user.mail:cancel_confirm Validatable ValidKeys: '<infer>'
user.mail:cancel_confirm.body Validatable Regex:
pattern: '/([^\PC\x09\x0a\x0d])/u'
match: false
message: 'Text is not allowed to contain control
characters, only visible characters.'↣ PrimitiveType: { }
user.mail:cancel_confirm.subject Validatable Regex:
pattern: '/([^\PC])/u'
match: false
message: 'Labels are not allowed to span multiple
lines or contain control characters.'
NotBlank: { }
↣ PrimitiveType: { }
user.mail:langcode Validatable NotNull: { }
Choice:
callback:
'Drupal\Core\TypedData\Plugin\DataType\LanguageReferenc
e::getAllValidLangcodes'↣ PrimitiveType: { }
user.mail:password_reset Validatable ValidKeys: '<infer>'
user.mail:password_reset.body Validatable Regex:
pattern: '/([^\PC\x09\x0a\x0d])/u'
match: false
message: 'Text is not allowed to contain control
characters, only visible characters.'↣ PrimitiveType: { }
user.mail:password_reset.subject Validatable Regex:
pattern: '/([^\PC])/u'
match: false
message: 'Labels are not allowed to span multiple
lines or contain control characters.'
NotBlank: { }
↣ PrimitiveType: { }
user.mail:register_admin_created Validatable ValidKeys: '<infer>'
user.mail:register_admin_created.body Validatable Regex:
pattern: '/([^\PC\x09\x0a\x0d])/u'
match: false
message: 'Text is not allowed to contain control
characters, only visible characters.'↣ PrimitiveType: { }
user.mail:register_admin_created.subject Validatable Regex:
pattern: '/([^\PC])/u'
match: false
message: 'Labels are not allowed to span multiple
lines or contain control characters.'
NotBlank: { }
↣ PrimitiveType: { }
user.mail:register_no_approval_required Validatable ValidKeys: '<infer>'
user.mail:register_no_approval_required.body Validatable Regex:
pattern: '/([^\PC\x09\x0a\x0d])/u'
match: false
message: 'Text is not allowed to contain control
characters, only visible characters.'↣ PrimitiveType: { }
user.mail:register_no_approval_required.subject Validatable Regex:
pattern: '/([^\PC])/u'
match: false
message: 'Labels are not allowed to span multiple
lines or contain control characters.'
NotBlank: { }
↣ PrimitiveType: { }
user.mail:register_pending_approval Validatable ValidKeys: '<infer>'
user.mail:register_pending_approval.body Validatable Regex:
pattern: '/([^\PC\x09\x0a\x0d])/u'
match: false
message: 'Text is not allowed to contain control
characters, only visible characters.'↣ PrimitiveType: { }
user.mail:register_pending_approval.subject Validatable Regex:
pattern: '/([^\PC])/u'
match: false
message: 'Labels are not allowed to span multiple
lines or contain control characters.'
NotBlank: { }
↣ PrimitiveType: { }
user.mail:register_pending_approval_admin Validatable ValidKeys: '<infer>'
user.mail:register_pending_approval_admin.body Validatable Regex:
pattern: '/([^\PC\x09\x0a\x0d])/u'
match: false
message: 'Text is not allowed to contain control
characters, only visible characters.'↣ PrimitiveType: { }
user.mail:register_pending_approval_admin.subject Validatable Regex:
pattern: '/([^\PC])/u'
match: false
message: 'Labels are not allowed to span multiple
lines or contain control characters.'
NotBlank: { }
↣ PrimitiveType: { }
user.mail:status_activated Validatable ValidKeys: '<infer>'
user.mail:status_activated.body Validatable Regex:
pattern: '/([^\PC\x09\x0a\x0d])/u'
match: false
message: 'Text is not allowed to contain control
characters, only visible characters.'↣ PrimitiveType: { }
user.mail:status_activated.subject Validatable Regex:
pattern: '/([^\PC])/u'
match: false
message: 'Labels are not allowed to span multiple
lines or contain control characters.'
NotBlank: { }
↣ PrimitiveType: { }
user.mail:status_blocked Validatable ValidKeys: '<infer>'
user.mail:status_blocked.body Validatable Regex:
pattern: '/([^\PC\x09\x0a\x0d])/u'
match: false
message: 'Text is not allowed to contain control
characters, only visible characters.'↣ PrimitiveType: { }
user.mail:status_blocked.subject Validatable Regex:
pattern: '/([^\PC])/u'
match: false
message: 'Labels are not allowed to span multiple
lines or contain control characters.'
NotBlank: { }
↣ PrimitiveType: { }
user.mail:status_canceled Validatable ValidKeys: '<infer>'
user.mail:status_canceled.body Validatable Regex:
pattern: '/([^\PC\x09\x0a\x0d])/u'
match: false
message: 'Text is not allowed to contain control
characters, only visible characters.'↣ PrimitiveType: { }
user.mail:status_canceled.subject Validatable Regex:
pattern: '/([^\PC])/u'
match: false
message: 'Labels are not allowed to span multiple
lines or contain control characters.'
NotBlank: { }
↣ PrimitiveType: { }
---------------------------------------------------- ------------- ---------------------------------------------------------11.x.composer require drupal/config_inspector— or manually install https://www.drupal.org/project/config_inspector/releases/2.1.5 or newer (which supports Drupal 11!)composer require drush/drushvendor/bin/drush config:inspect --filter-keys=user.mail --detail --list-constraintsAdd validation constraints to:
user.mailNone
None.
None.
More validation 🚀
None.
The long description for \Drupal\Tests\UnitTestCase is the following one.
Using Symfony's dump() function() in Unit tests will produce output on the command line.
The parentheses after function must be removed.
system.site has 5 property path that are not yet validatable:
vendor/bin/drush config:inspect --filter-keys=system.site --detail --list-constraints
➜ 🤖 Analyzing…
Legend for Data:
✅❓ → Correct primitive type, detailed validation impossible.
✅✅ → Correct primitive type, passed all validation constraints.
---------------------------------------- --------- ------------- ------ ---------------------------------------------------------------------------------------------
Key Status Validatable Data Validation constraints
---------------------------------------- --------- ------------- ------ ---------------------------------------------------------------------------------------------
system.site Correct 69% ✅❓ ValidKeys: '<infer>'
LangcodeRequiredIfTranslatableValues: null
system.site: Correct Validatable ✅✅ ValidKeys: '<infer>'
LangcodeRequiredIfTranslatableValues: null
system.site:_core Correct Validatable ✅✅ ValidKeys:
- default_config_hash
system.site:_core.default_config_hash Correct Validatable ✅✅ NotNull: { }
Regex: '/^[a-zA-Z0-9\-_]+$/'
Length: 43
↣ PrimitiveType: { }
system.site:admin_compact_mode Correct Validatable ✅✅ ↣ PrimitiveType: { }
system.site:default_langcode Correct Validatable ✅✅ NotNull: { }
Choice:
callback: 'Drupal\Core\TypedData\Plugin\DataType\LanguageReference::getAllValidLangcodes'↣ PrimitiveType: { }
system.site:langcode Correct Validatable ✅✅ NotNull: { }
Choice:
callback: 'Drupal\Core\TypedData\Plugin\DataType\LanguageReference::getAllValidLangcodes'↣ PrimitiveType: { }
system.site:mail Correct Validatable ✅✅ Email:
message: '%value is not a valid email address.'↣ PrimitiveType: { }
system.site:mail_notification Correct NOT ✅❓ ⚠️ @todo Add validation constraints here
system.site:name Correct Validatable ✅✅ Regex:
pattern: '/([^\PC])/u'
match: false
message: 'Labels are not allowed to span multiple lines or contain control characters.'↣ PrimitiveType: { }
system.site:page Correct Validatable ✅✅ ValidKeys: '<infer>'
system.site:page.403 Correct NOT ✅❓ ⚠️ @todo Add validation constraints here
system.site:page.404 Correct NOT ✅❓ ⚠️ @todo Add validation constraints here
system.site:page.front Correct NOT ✅❓ ⚠️ @todo Add validation constraints here
system.site:slogan Correct Validatable ✅✅ Regex:
pattern: '/([^\PC])/u'
match: false
message: 'Labels are not allowed to span multiple lines or contain control characters.'↣ PrimitiveType: { }
system.site:uuid Correct Validatable ✅✅ Uuid: { }
NotNull: { }
↣ PrimitiveType: { }
system.site:weight_select_max Correct NOT ✅❓ ⚠️ @todo Add validation constraints here
---------------------------------------- --------- ------------- ------ ---------------------------------------------------------------------------------------------
11.x.composer require drupal/config_inspector— or manually install https://www.drupal.org/project/config_inspector/releases/2.1.5 or newer (which supports Drupal 11!)composer require drush/drushvendor/bin/drush config:inspect --filter-keys=system.site --detail --list-constraintsAdd validation constraints to:
system.site:mail_notificationsystem.site:page.403system.site:page.404system.site:page.frontsystem.site:weight_select_maxFor examples, search *.schema.yml files for the string constraints:😊
Reach out to @borisson_ or @wimleers in the #distributions-and-recipes.
None.
More validation 🚀
None.
core.menu.static_menu_link_overrides has 3 property path that are not yet validatable:
./vendor/bin/drush config:inspect --filter-keys=core.menu.static_menu_link_overrides --detail --list-constraints
➜ 🤖 Analyzing…
Legend for Data:
✅❓ → Correct primitive type, detailed validation impossible.
✅✅ → Correct primitive type, passed all validation constraints.
-------------------------------------------------------------------------------- --------- ------------- ------ --------------------------------------------
Key Status Validatable Data Validation constraints
-------------------------------------------------------------------------------- --------- ------------- ------ --------------------------------------------
core.menu.static_menu_link_overrides Correct 70% ✅❓ ValidKeys: '<infer>'
LangcodeRequiredIfTranslatableValues: null
core.menu.static_menu_link_overrides: Correct Validatable ✅✅ ValidKeys: '<infer>'
LangcodeRequiredIfTranslatableValues: null
core.menu.static_menu_link_overrides:_core Correct Validatable ✅✅ ValidKeys:
- default_config_hash
core.menu.static_menu_link_overrides:_core.default_config_hash Correct Validatable ✅✅ NotNull: { }
Regex: '/^[a-zA-Z0-9\-_]+$/'
Length: 43
↣ PrimitiveType: { }
core.menu.static_menu_link_overrides:definitions Correct NOT ✅❓ ⚠️ @todo Add validation constraints here
core.menu.static_menu_link_overrides:definitions.contact__site_page Correct Validatable ✅✅ ValidKeys: '<infer>'
core.menu.static_menu_link_overrides:definitions.contact__site_page.enabled Correct Validatable ✅✅ ↣ PrimitiveType: { }
core.menu.static_menu_link_overrides:definitions.contact__site_page.expanded Correct Validatable ✅✅ ↣ PrimitiveType: { }
core.menu.static_menu_link_overrides:definitions.contact__site_page.menu_name Correct NOT ✅❓ ⚠️ @todo Add validation constraints here
core.menu.static_menu_link_overrides:definitions.contact__site_page.parent Correct NOT ✅❓ ⚠️ @todo Add validation constraints here
core.menu.static_menu_link_overrides:definitions.contact__site_page.weight Correct Validatable ✅✅ Range:
min: -2147483648
max: 2147483647
FullyValidatable: null
↣ PrimitiveType: { }
-------------------------------------------------------------------------------- --------- ------------- ------ --------------------------------------------
11.x.composer require drupal/config_inspector— or manually install https://www.drupal.org/project/config_inspector/releases/2.1.5 or newer (which supports Drupal 11!)composer require drush/drushvendor/bin/drush config:inspect --filter-keys=core.menu.static_menu_link_overrides --detail --list-constraintsAdd validation constraints to:
definitionsmenu_nameparentFor examples, search *.schema.yml files for the string constraints:😊
Reach out to @borisson_ or @wimleers in the #distributions-and-recipes.
None.
More validation 🚀
None.
The postgres implementation of introspectIndexSchema returns columns in the order of column name rather than in the order that columns are in the index. This makes writing tests that run on multiple dbs harder than it should be and also makes postgres tests that use it less of a proper test because the order of columns is significant.
With drupal 10.3 and the Patch/MR from #2916876: Add visibility control conditions to blocks within Layout Builder I am able to add visibilty conditions in layout_builder. This works fine for non-navigation layout builder. From this I assume, it also should work with navigation blocks.
Patches/MR tested:
When I add a condition to a navigation block, I get a WSOD on any page with the navigation:
Drupal\Component\Plugin\Exception\ContextException: Assigned contexts were not satisfied: user in Drupal\Core\Plugin\Context\ContextHandler->applyContextMapping() (line 145 of /home/andi/git/site-h4d-greenopolis/web/core/lib/Drupal/Core/Plugin/Context/ContextHandler.php).
/admin/config/user-interface/navigation-blockBuild test, Command/GenerateThemeTest.php is failing on SQLite and 10.3.x. The test estContribStarterkitDevSnapshotWithGitNotInstalled
Drupal\BuildTests\Command\GenerateThemeTest::testContribStarterkitDevSnapshotWithGitNotInstalled
Fake git used by process.
Failed asserting that 0 matches expected 127.
core/tests/Drupal/BuildTests/Command/GenerateThemeTest.php:291
https://git.drupalcode.org/project/drupal/-/pipelines/215476/test_report...
php Error LogicException: The mapping definition at
`ckeditor5.plugin.ckeditor5_list:properties` is invalid: its `label`
key contains a string. It must be an array. in
Drupal\Core\Config\Schema\MappSince 10.3 upgrade
Across the admin interface there are several pages with buttons with a grey background color, regular buttons as well as drop buttons. all with a background-color of #C1C2C7 on either on a white backgroud #FEFFFE (1.8:1) or light blueish table headers #f3f4f9 (1.6:1). In each case that fails WCAG21 SC 1.4.11 which requires a contrast ratio of 3:1.
I've asked @mgifford for feedback and advice about the buttons cuz I was uncertain if I was overcautious or if it is a necessary step. But he confirmed that the grey buttons either need an outline with more contrast or more contrast for the background color. Either should be fine and he doesn't have a strong preference and he doesn't know which would be best for the design. I'll add aside the Accessibility tag also the needs design tag since aside the change of color there also needs to be some design decision.
- go for example to admin/structure/views/view/content or admin/content
- check the background color of the grey buttons
