🇫🇷France @GPZ

Updated the last patch to support the new filter "Only blocked"
I did this the same way it is done in "dev" if I'm right.
(This means it's display filter only, not a request filter)

Sorry, patch name includes now the ticket number and comment number

GPZ → created an issue.

Patch to ignore some assets routes

GPZ → created an issue.

In my case this patch resolves the multiple display of "Allowed types"
but if I try to upload a svg file is FileIsImage validator says it is not valid and return an error about the type not part of
$supportedExtensions = $this->imageFactory->getSupportedExtensions();
which does not contains "svg"
without this patch I have the double display but in the end it works

I've found this core patch:
https://www.drupal.org/project/drupal/issues/3399951 🐛 ajax_page_state leaks through request in Views Ajax Needs work
and it fixes the issues for me (both overlay and JS added to DOM at each Ajax request)

I have the same issue.
see before and after screenshots.
I'm using Drupal 10.2.1 but still using the module contrib seven for the BO theme.
The problem seems to be the css order
At first ".ui-dialog" from seven override .ui-front from core jquery.ui (important part is the z-index: 1260 from ui-dialog and 100 for the other one.
but once you click on the pager the order is reversed and .ui-front overrides .ui-dialog and the final z-index is 100 while ui-widget-overlay (the black overlay that should be behind the dialog) is 1259

I've tried with claro and the problem doesn't appear but that's because the .ui-dialog from theme seems to appear twice. One after the core.css and one before (see screenshot). It seems to add more claro/css/components/jquery.ui/theme.css after each pager usage. My claro theme is not full working so, I'm not sure if this is revelant

The patch seems to be applied in version 6.1.5 but not in 6.2.x
Applying the patch in 6.2.2 works

GPZ → created an issue.

D10 version for 2x branch

Same problem here, With drupal 9.5 and the JSONAPI we had no problem (but the duration field was null).
with drupal D10.1.5 we ran into the same prvious error message in the JSONAPI.
And the patch fixed the error and also now the duration field is not null

                "field_duration": {
                    "seconds": 3600,
                    "duration": "PT1H"
                },

GPZ → created an issue.