🇫🇷France @damien laguerre

Thanks for your feedback!
Yes, I've made a commit to fix your second point.
The new version contains both corrections.

The deprecation in SimplenewsStatsPage was solved here: https://www.drupal.org/project/simplenews_stats/issues/3442000 🐛 Deprecated function: Creation of dynamic property Drupal\simplenews_stats\SimplenewsStatsPage Fixed
What version of the module are you using?

First, thanks for your works!

I tried your patch and implemented the function mymodule_entity_clone_clonable_fields_alter(array &$fields)
But that's not enough, for this to work I need to clear the new entity field using a bundle class with a custom createDuplicate:

  /**
   * {@inheritdoc}
   */
  public function createDuplicate() {
    $duplicate = parent::createDuplicate();

    $duplicate->set('field_paragraph', null);

    return $duplicate;
  }

Otherwise, the field is not cloned by entity_clone, but is already filled by the core duplication.

Applied the patch on Drupal 10.3.5 + commerce 2.40 and everything works fine.
Very useful, thank you!

Thank you for your help and the time you spent on my module.
I really appreciate it!

Thanks again.

It's done!

Thanks to all those who took the time for this little module.

The security coverage is in progress:
https://www.drupal.org/project/projectapplications/issues/3441891 →

You can help it with code review.

Sorry, My bad, it's for the 2.0.x version.

Damien Laguerre → created an issue.

Thanks, it's fixed.

Thank you for your time and sorry for the delay.

I've made all the changes. Everything is visible on the repository, I haven't made any release yet.

Idem, #43 solved my problem.
I'm experiencing this problem in a REST resource. The context user.node_grants:view throws this error.

Yes, there was a problem with the variable names.

Thanks for the work!

Damien Laguerre → created an issue.

I've released new version for Simplenews 4.0.

Simple but effective!
Reviewed and tested.

The error occurs in the loggin screen. Look at the console before submitting it.

In the case of Gin the problem is visible in the console.

Antibot use JavaScript, checks your console, you must have a JS error.

I've also encountered a similar problem.

This ticket fixes the problem:
https://www.drupal.org/project/gin/issues/3432512 🐛 Missing once dependencies on sticky and gin_accent libraries even tho it uses it Fixed

I also applied the patch to 4 sites two days ago, and the spam was all blocked.
Everything seems to be working perfectly.

Thanks for the patch.

I encounter a similar issue with a view facets filter.

Everything works fine, except if I want to apply the action to all result pages.
The facets module does not identify which facets filters are active on the batch route.

I found a (quick and maybe dirty) solution by passing the "f" parameter to the query.

In the case of an anonymous customer, using the users field does not work.
Using the information contained in the Address field of the profile may be a good solution.

'FirstName' => $address['given_name'],
'LastName' => $address['family_name'],

To remain compatible with all sites using ipless, I've implemented the hook_config_schema_info_alter to include to system.performance schema the ipless config description.

Damien Laguerre → created an issue.

Fixed, thanks!

Merged, thanks!

Damien Laguerre → made their first commit to this issue’s fork.

I think the error here is the migration ID

d7_node_complete must be replaced by the migration ID upgrade_d7_node_complete_page

id: upgrade_d7_node_complete_page
migration_group: migrate_drupal_7
label: 'Node complete (Basic pages)'
source:
  plugin: d7_node_complete
  node_type: page
process:
  nid:
     -
       plugin: migration_lookup
       migration: upgrade_d7_node_complete_page <<-- Must match the migration ID
       source: tnid
     -
       plugin: node_complete_node_lookup

You have this error because your files directory is not writable.
As I say in your previous ticket, you have to checks your public:// directory permission.

This is caused by the "Watch mode".
If you are on production, you have to disable this functionality in
Configuration > Development > Performance

But the error indicates that you can't write to your file directory.
web/sites/default/files

Checks the permissions of your directory.
Something like this might help. Adapt the permissions to your environment.
chmod 775 web/sites/default/files

I had the same issue with Drupal 10 and php 8.1.
I confirm that using the dev version solved the issue.

Thanks!

All possible groups are :

• base
• layout
• component
• state
• theme

In your case, you have a library with "components" group key.
If your site is working fine with ipless disabled, it means that you have a library like this one:

base:
  less:
    components: <---
      css/components/foo.css:

You can try something like this and you'll get the same error:

base:
  css:
    foo: <---
      css/components/foo.css:

'Error: Undefined constant "CSS_FOO" in constant() (line 180 of

This is not an error of the module, but an error in a lbrary.

I think this is a mistake in the definition of a library.

The "component" key does not have an S at the end.

base:
  css:
    component: <---
      css/components/foo.css:

Thank you. I hope this will be merged in a next release.

Great!

2. I discovered that in Drupal the service_collector tag corresponds to tagged_iterator in Symfony. Use this instead of creating a compiler pass.

I first tried this way, but it could not be used with all the Symfony services I defined the first time.
Now it's really the best solution.

I did some tests and everything works fine!