🇬🇧United Kingdom @Alina Basarabeanu

Thank you Luca
Please see my logs

I can't find any logs on the server
How do I set the --log-dir?

alina basarabeanu → created an issue.

A new patch for Drupal Core 10.3.7 was generated from 2730351-D10.3.x-134 patch

A new patch for the Drupal core 10.3.6

A new patch created for Drupal Core 10.3.6

Hi
Can anyone provide a patch for Drupal Core 10.3?
None of the above applies and I can not upgrade the project.

The changes from the issue don't apply to the 2.0.3 version.
Switching to 2.x-dev fixed the error

ArgumentCountError: Too few arguments to function Drupal\seckit\EventSubscriber\SecKitEventSubscriber::__construct(), 2 passed in /var/www/html/docroot/core/lib/Drupal/Component/DependencyInjection/Container.php on line 261 and exactly 3 expected in Drupal\seckit\EventSubscriber\SecKitEventSubscriber->__construct() (line 70 of modules/contrib/seckit/src/EventSubscriber/SecKitEventSubscriber.php).

Updated patch for the 2.x-dev version

Updated patch for version 2.11

alina basarabeanu → created an issue.

The patch from #3 works as expected on Drupal 10.2.2 and Path redirect import 2.0.9

The patch from #31 is working on Drupal 10.2.2 and Honeypot 2.1.3

We used the code changes from merge request 29 and worked as expected on Drupal core 10.2.2 and S3fs 3.4.0.
We did not want to have the VersionId attached to the file

Works on Drupal core 10.2.2 and Social Media Links Block 2.9.0

The patch from #35 is working on Drupal 10.2.2 and Seckit 2.0.1.

Can we have a stable version of this module for Drupal 10?
The patch is working fine on Drupal 10.2.2

The patch works as expected on the Drupal version 10.2.5 and Site Guardian 1.0.4.

Alina Basarabeanu → created an issue.

A new patch was created to work on diff version 1.3.0

1. "2944938: Default lifetime for permanent items for Drupal 8": " https://www.drupal.org/files/issues/2020-09-23/redis-default_permanent_t... → ",
2. "3163436: Connection refuse in PhpRedis when sentinel/redis are down": " https://www.drupal.org/files/issues/2023-09-13/Add_a_Redis_connection_te... → ",
3. "3175412: Use item_id instead of qid for Queue item": " https://www.drupal.org/files/issues/2020-10-07/redis-queue-item-id-31754... → ",
4. "3154093: Add a dedicated permission for accessing redis report": " https://www.drupal.org/files/issues/2020-06-23/3154093-redis-perm.patch → ",
5. "3192255 & 3173988: Wrong memory percentage on /admin/reports/redis": "patches/Merge_issue_3192255_and_3173988_into_one_patch_.patch",
6. "3004561: Support TLS for Predis": " https://www.drupal.org/files/issues/2021-11-19/redis-support_tls_on_pred... → "

Alina Basarabeanu → created an issue.

Alina Basarabeanu → created an issue.

We are getting this error on version 1.3.0
The patch fixed the issue.

This issue is blocking the slick version 3 and blazy version 3

The patch from #2 fixed the issue on the Drupal Version 10.2.2 and SHS 2.0.0-rc4

This patch was included in version 1.1.8.
Can you mark this ticket as closed and fixed?

This issue seems to be fixed with the bat 8.x-10.1-rc3 version.

Don't know why this query parameter was necessary but looks like is not used anymore.
I created a patch to remove the query parameter.

Alina Basarabeanu → created an issue.

Yes,
Previously I was using the merge request as was pointing to 10.x branch.
Thanks

With the changes pushed with the last commit, we could not apply the patch to Drupal Core 10.2.3.
Can you please add a patch file for 10.2.3 version?

6 months later still no new version.
I've noticed a few other issues reviewed and tested by the community.

We have been using the patch from #10 for the last 2 years.
The calculation from issue 3179757 is the same as the one done in this issue.
Would be good to have one of them merged into a stable version.
Currently, we are using 7 patches to make this module work.

A new patch was added.

Alina Basarabeanu → created an issue.

Hi @Damien
Any progress with this issue?
We have been seeing double error messages for the file extension validation since upgrading to core 10.2.1

Using Drupal 10.2 and PWA 2.1.0-beta3 we only get the visited page cached and available when offline.
I tried to populate the "URLs to cache on install" with "/" or left empty.

In our case, the missing part was the permissions for the anonymous user for 'Access PWA'.
Also, make sure that you enable the sub-module 'pwa_service_worker'.

I can't get it to work.
No manifest.json was generated when enabling the module.
How do I check that the Service Worker is active? I enabled the sub-module pwa_service_worker
I saved the pwa.config.yml file and pushed it to the environment, but the website is unavailable when offline.

Just discovered that the latest patch breaks the XML sitemap.
When viewing the website sitemap in Firefox an error is shown: XML Parsing Error: not well-formed
Set the defer attribute as defer="defer" instead of just 'defer' for the seckit.frame_check.js file.
Updated patch added.

Alina Basarabeanu → created an issue.

Alina Basarabeanu → created an issue.

The patch fixed the form for us.
Please add this to a new stable version.

Having the same use case as @shivamitakari. Our clients want to keep their TFA settings when we copy the database from production to the other environments.
A new patch was created for version 2.x.

We came across this issue on multiple projects using D10.2 and the entity browser 2.9.0
Tested on older Drupal core versions and entity browser we get the error too.
The patch from #6 solved the error for a field type Entity reference to a media on a content type. The widget used by the Form display is 'Entity Browser'.

We came across the same error after upgrading to Drupal core 10.2.
The patch provided by #9 fixed the issue.
Please add this to a new stable release.

The changes from the patch are included in the 3.0@beta version.
Will close this ticket as fixed.

The patch is only working with ief_table_view_mode:3.0.x-dev@dev version.
We have not had a stable release for over a year but there are 2 new dev branches.
Can we have a new release?

Closing as is fixed on bat_api 3.1.0-rc1.
core_version_requirement: ^9 || ^10

Hi Augusto
The changes have been added to the latest version bee 8.x-3.0-beta3.
Can you please mark this issue as fixed?

Patch created

Alina Basarabeanu → created an issue.

A new patch was created to include only changes to the form-action directive.
The base-uri directive is added with issue 3098417.
The script-src-elem is added with issue 3208781.
The manifest-src should be added with a new issue.

The patch fixed the Ajax error on Drupal 10.2, the Gin theme 8.x-3.0-rc8 and the Gin Layout Builder 1.0.0-rc5.
As mentioned above the Gin Layout Builder modified the ID for the secondary toolbar to "gin-secondary-toolbar" and the code from the toolbar.js fails to find the element in the DOM.
It is always safer to check if the element exists before applying a style.
We will use the patch from #2 to fix the issue.

Hi @BramDriesen
I just updated to Drupal 10.2 and the

Many thanks, @ben_a

Hi @wim-leers
How can I generate a patch for the Drupal 10.2 version?

+1 for a release

Thank you for the patch. That saved my day.
Will revise all my patches using a pull request (lesson learned).

By changing the branch from 10.1 to 11 the patch failed to apply because of the conflicts.
We heavily use this functionality on our 10.1 website. Can we have it back for 10.1?

Patch #6 is working fine on Drupal 10.1.6 with Seckit 2.0.1

I can replicate this issue as an anonymous user.
The controller shs.term_data uses the 'access content' permission, so doesn't make sense why we need the 'access toolbar' to be able to access the term data.

Alina Basarabeanu → created an issue.

I am getting the error on Drupal Version 10.1.6 and Search API 1.30.

RuntimeException while trying to render item entity:node/123:en with view mode default for search index Main index: Failed to start the session because headers have already been sent by "/var/www/html/vendor/symfony/http-foundation/Response.php" at line 426. in Symfony\Component\HttpFoundation\Session\Storage\NativeSessionStorage->start() (line 132 of /var/www/html/vendor/symfony/http-foundation/Session/Storage/NativeSessionStorage.php).

EntityInterface no longer has isPublished() method. Only the EntityPublishedInterface

Alina Basarabeanu → created an issue.

The changes from the merge request !6 fixed the issue on Drupal 10.1.5 and Redirect 1.9.0.

We came across this issue using Drupal 10.1.5 and Redirect 1.9.0.
I created a new redirect from /old-page to /new-page but when navigating to /old-page I still can view the page.
The only change on the page is the breadcrumb pointing to the new page.
I did clear the cache and even ran cron but the redirect is not triggered.
Applying the patch from #149 fixed the redirect but the URL redirect is not added to either node's edit form.

This issue is not present on the inline_entity_form 1.0.0-rc15 version. We downgraded back to this version.

I can replicate this issue on Drupal 10.1.5 and inline_entity_form 2.0.0-rc9

We came across this issue too.
The latest Claro variables.css file contains colours used for the jQuery.UI dropdown which are not loaded inside the layout builder modal.
We had to include the '/core/themes/claro/css/base/variables.css' file within our custom theme.

Thanks for pointing that out. We are using an old patch for the issue 3062604. I updated to the latest patch version and this issue is fixed.
Please close this one.

Alina Basarabeanu → created an issue.

A new pull request was opened to fix the error:
Error: Call to a member function label() on array in Drupal\bat_unit\Plugin\views\field\BatTypeHandlerTypeCalendarsField->render() (line 85 of modules/contrib/bat/modules/bat_unit/src/Plugin/views/field/BatTypeHandlerTypeCalendarsField.php).

Patch created as I couldn't pull the fork branch.

Alina Basarabeanu → created an issue.

The error reported by #4 is fixed with the issue 3382684.
The current pull request is fixing D10 compatibility only.
We need those changes in a new stable version to use the module on Drupal 10.

The patch is fixing the PHP fatal error.
Please create a new release as the module can't be used in D10.

This pull request should cover the fixes for the 3369194 & 3391008 issues.

Alina Basarabeanu → created an issue.

A patch was created to fix the error.
The constant MASTER_REQUEST is deprecated and it was replaced with MAIN_REQUEST in BatApiMiddleware class.

Using bat_api 1.3.0, with 2 patches for issue 3348451 & 3286204 on D10 we get a fatal error:
Fatal error: Declaration of Drupal\bat_api\StackMiddleware\BatApiMiddleware::handle(Symfony\Component\HttpFoundation\Request $request, $type = self::MASTER_REQUEST, $catch = true) must be compatible with Symfony\Component\HttpKernel\HttpKernelInterface::handle(Symfony\Component\HttpFoundation\Request $request, int $type = self::MAIN_REQUEST, bool $catch = true): Symfony\Component\HttpFoundation\Response in /var/www/html/docroot/modules/contrib/bat_api/src/StackMiddleware/BatApiMiddleware.php on line 37

This module is not up to date and very difficult to keep it up to the latest changes to Drupal.
Can someone have a look at all the patches and create a new D10 stable version?