🇩🇪Germany @kreatIL

I have implemented the solution outlined in comment #12 and can confirm that it successfully bypasses the error message, allowing updb to run without any issues.

I am experiencing the same issue as described here. I have tested this with the latest 3.x-dev version of the module, but the problem persists. Drupal 10.3.10 in my usecase.

Additionally, I have created a patch based on the changes provided in commit #6 and applied it to my site. Unfortunately, the error still occurs after applying the patch.

Updating the status of this issue to "needs work"

kreatil → created an issue.

It appears there has been a misunderstanding regarding the behavior of the /admin/people/simplenews page. By default, this page displays all subscribers, regardless of whether they are actively subscribed to a specific newsletter channel. This default behavior can give the impression that the total number includes only active channel subscribers, which is not the case.

I hope this clarifies the situation, and I apologize for any confusion caused by this misunderstanding.

kreatil → created an issue.

The workaround described in the issue worked perfectly for me. Downgrading first to version 2.1.4, running the database updates, and then upgrading to 2.2.0 resolved the problem without issues. Thanks for documenting this!

I maintain a Drupal site with around 30,000 media entities, which constitute approximately 95% of our content. The Visitors module would be incredibly useful for us to track and analyze user interactions with this content.

I appreciate the discussion here about extending entity types, and I want to echo the value of this enhancement. Supporting media entities would allow us to gain detailed insights into user engagement across all content types, making Visitors a powerful tool for a wider range of Drupal sites.

#31: +1
We have been using Entity Reference Purger → in production for over a year. The module addresses exactly the issue described in the original post. In our usecase, the number of references to be deleted is typically in the triple digits, without any significant performance issues.

Patch #57 is working for me

To be honest, looking at the number of fatal errors that people are reporting, this module doesn't feel very stable to me.

However, with over 46K websites using this module and the number still growing, doesn’t that suggest the module is stable enough? A stable release would be highly appreciated.

Thank you. I had been searching for an issue about that but didn't find one. Anyway, good to hear that this has been solved.

kreatIL → created an issue.

Yes, it seems to be fixed by Drupal core 10.2.1

At the moment there is a lack of good end-use documentation and a growing number of confused people elsewhere who have given up and just disabled it.

I would totally agree with that.

After a thorough review of the available information and attempts to understand this issue, I have concerns regarding the feasibility of reproducing the error, particularly since it seems to predominantly affect sites that have been upgraded from Drupal 8 or Drupal 9.

From what I've gathered, this error does not readily manifest in fresh installations of Drupal 10, which suggests that it might be tied to specific configurations or legacy data from older versions. This makes it challenging to replicate the conditions necessary to observe the error in a controlled environment.

Patch #29 does not add any new functionality, but merely checks whether $break->operator is set. Which appears to have successfully resolved the issue for many who have applied it, indicating its effectiveness in addressing this specific error.

Given these circumstances, I would like to propose a consideration for the integration of Patch #29 into core.

#29 fixed the issue for me too.

The patch cannot be applied due to at least one issue: In Version 10.2.x, Line 228 (which corresponds to Line 208 in Version 10.1.x) has been modified. It now reads:
keys(['nid' => $node->id(), 'tid' => $tid, 'status' => $node->isPublished()])
It's important to note that the function is "keys" in Version 10.2.x, as opposed to "key" which was used in Version 10.1.x.

I came across this issue having a similar question. The hints given in #2 solved it for me. I think this issue can be marked as solved.

@catch: Thanks for the clarification. Although I would find it easier if such messages did not appear at all in the logs.

I get exactly this error as well since the update from Drupal 9.5 to 10.1. My website runs on a NGINX webserver and I have already disabled the js/css aggregation - without success. This error has been appearing in the log for weeks.

Yes, #11 did the trick.

In my case, the method described under #23 also worked. However, afterwards I had to reactivate symfony_mailer_bc and go to admin/config/system/mailer/override and perform "User" > "Enable & Import". Why symfony_mailer_bc now has to be active again, even though it was declared as obsolete, is beyond me.

@dimitriskr: I don't know. I was added as maintainer here by accident.

I'm going to replace vapn by permissions_by_term → in my project. So the issue (unable to update to D10) will be fixed for me within next days.

@smulvih2: Thank you for submitting the patch. I've tested it in my environment, and it successfully fixed the token replacement issue I was experiencing.

I'm not sure if this is related, but after updating to 8.x-1.7, the arrows that indicate the presence of a submenu have disappeared on my site. This doesn't seem to be a CSS issue, as the entire HTML tags are no longer being rendered.

Reverting back to 8.x-1.6 resolves the issue for me as well.

Can someone confirm that? If needed, I'm happy to open a separate issue for this.

Please add andrechun as maintainer. He offered it. I just wanted to give support to his offer.

I would appreciate that. This module is currently blocking the upgrade to Drupal 10 in one of my projects.

Patch #4 does not apply against version 2.0.1. New patch should apply.

I think this is relating to Global tokens not replaced 🐛 Global tokens not replaced RTBC

I can also confirm patch #2 fixes the issue. In my case [current-date:custom] did not get replaced at first. With the patch being applied it works like a charm. Thank you.

3.1.22 breaks functionality also in my case with drupal 9.5.10. Cannot review the proposed solution because there is no patch provided here.

@Rajab: Thanks for your feedback. In my case, the error described in this issue did not go away by applying the patch from 🐛 Circular reference detected for service symfony mailer config override in multilingual sites Fixed . I had to apply the patch from 🐛 Update emails not working Fixed

But it would be good if other people could review this, as I can't rule out other factors for sure.

I have strong evidence this is related to an issue belonging to symfony_mailer: " Update emails not working 🐛 Update emails not working Fixed "

After applying the patch, I did not get any more error messages on cron run.

kreatIL → created an issue.

RTBC +1 Thank you.

I managed to get it running by:
- uninstall my custom module containing the callback function
- add config file to custom/mymodule/config/optional/ultimate_cron.job.cron_job_name.yml
- re-install my custom module
The cron job appeared in the list of jobs under /admin/config/system/cron/jobs even without triggering "Discover jobs".
- edit job configuration
- drush cex

To narrow down the error further, I have manually triggered the jobs listed under /admin/config/system/cron/jobs one after the other. The error occurs with the cronjob, which is named in the table with "Update indexes" (Update Manager).

@Londova: Thank for the hint you've given in #6. I already had the latest version of simple_sitemap running and even the latest dev version doesn't solve the issue for me.

Facing the same issue on Drupal 9.5.10, PHP 8.1.16 and Ultimate Cron Version: 8.x-2.0-alpha6

I can confirm patch #25 fixes the error. Thank you @metallized

Forwarding to dev-1.x 9b1509d does not solve it.

This is the error message that I get when I try to clear caches via admin ui:

Symfony\Component\DependencyInjection\Exception\ServiceCircularReferenceException: Circular reference detected for service "language_manager", path: "language_manager -> config.factory -> symfony_mailer.config_override -> plugin.manager.email_builder -> entity_type.manager -> string_translation -> string_translator.locale.lookup". in Drupal\Component\DependencyInjection\Container->get() (line 147 of core/lib/Drupal/Component/DependencyInjection/Container.php).

Drupal\Component\DependencyInjection\Container->get('language_manager', 1) (Line: 434)
Drupal\Component\DependencyInjection\Container->resolveServicesAndParameters(Array) (Line: 237)
Drupal\Component\DependencyInjection\Container->createService(Array, 'string_translator.locale.lookup') (Line: 177)
Drupal\Component\DependencyInjection\Container->get('string_translator.locale.lookup', 1) (Line: 434)
Drupal\Component\DependencyInjection\Container->resolveServicesAndParameters(Array) (Line: 273)
Drupal\Component\DependencyInjection\Container->createService(Array, 'string_translation') (Line: 177)
Drupal\Component\DependencyInjection\Container->get('string_translation', 1) (Line: 434)
Drupal\Component\DependencyInjection\Container->resolveServicesAndParameters(Array) (Line: 237)
Drupal\Component\DependencyInjection\Container->createService(Array, 'entity_type.manager') (Line: 177)
Drupal\Component\DependencyInjection\Container->get('entity_type.manager', 1) (Line: 434)
Drupal\Component\DependencyInjection\Container->resolveServicesAndParameters(Array) (Line: 237)
Drupal\Component\DependencyInjection\Container->createService(Array, 'plugin.manager.email_builder') (Line: 177)
Drupal\Component\DependencyInjection\Container->get('plugin.manager.email_builder', 1) (Line: 434)
Drupal\Component\DependencyInjection\Container->resolveServicesAndParameters(Array) (Line: 237)
Drupal\Component\DependencyInjection\Container->createService(Array, 'symfony_mailer.config_override') (Line: 177)
Drupal\Component\DependencyInjection\Container->get('symfony_mailer.config_override', 1) (Line: 434)
Drupal\Component\DependencyInjection\Container->resolveServicesAndParameters(Array) (Line: 273)
Drupal\Component\DependencyInjection\Container->createService(Array, 'config.factory') (Line: 177)
Drupal\Component\DependencyInjection\Container->get('config.factory', 1) (Line: 434)
Drupal\Component\DependencyInjection\Container->resolveServicesAndParameters(Array) (Line: 237)
Drupal\Component\DependencyInjection\Container->createService(Array, 'language_manager') (Line: 177)
Drupal\Component\DependencyInjection\Container->get('language_manager') (Line: 613)
Drupal::languageManager() (Line: 479)
token_tokens('log', Array, Array, Array, Object)
call_user_func_array(Object, Array) (Line: 426)
Drupal\Core\Extension\ModuleHandler->Drupal\Core\Extension\{closure}(Object, 'token') (Line: 405)
Drupal\Core\Extension\ModuleHandler->invokeAllWith('tokens', Object) (Line: 433)
Drupal\Core\Extension\ModuleHandler->invokeAll('tokens', Array) (Line: 359)
Drupal\Core\Utility\Token->generate('log', Array, Array, Array, Object) (Line: 241)
Drupal\Core\Utility\Token->doReplace(1, '[[log:created]] [[log:level]] [[log:channel]] [client: [log:ip], [log:user]] [log:location] [log:message]', Array, Array, Object) (Line: 191)
Drupal\Core\Utility\Token->replace('[[log:created]] [[log:level]] [[log:channel]] [client: [log:ip], [log:user]] [log:location] [log:message]', Array, Array, Object) (Line: 223)
Drupal\filelog\Logger\FileLog->render(3, '%type: @message in %function (line %line of %file).', Array) (Line: 159)
Drupal\filelog\Logger\FileLog->log(3, '%type: @message in %function (line %line of %file).', Array) (Line: 127)
Drupal\Core\Logger\LoggerChannel->log(3, '%type: @message in %function (line %line of %file).', Array) (Line: 70)
Drupal\Core\EventSubscriber\ExceptionLoggingSubscriber->onError(Object) (Line: 97)
Drupal\Core\EventSubscriber\ExceptionLoggingSubscriber->onException(Object, 'kernel.exception', Object)
call_user_func(Array, Object, 'kernel.exception', Object) (Line: 142)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.exception') (Line: 229)
Symfony\Component\HttpKernel\HttpKernel->handleThrowable(Object, Object, 1) (Line: 92)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 50)
Drupal\ban\BanMiddleware->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel->handle(Object, 1, 1) (Line: 718)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

Same or similar issue here after upgrading to 1.3.0-rc1 on Drupal 9.5.10 and PHP 8.1.16
Circular reference detected for service "entity_type.manager", path: "scheduler.manager -> date.formatter -> entity_type.manager -> string_translation -> string_translator.locale.lookup -> config.factory -> symfony_mailer.config_override -> plugin.manager.email_builder".

It took me four hours to figure this out, because at first I assumed the error was caused by scheduler. Now I can definitely break it down to the update from symfony_mailer-1.3.0-beta2 to symfony_mailer-1.3.0-rc1.

Same or similar issue here after upgrading to 1.3.0-rc1 on Drupal 9.5.10 and PHP 8.1.16

Circular reference detected for service "entity_type.manager", path: "scheduler.manager -> date.formatter -> entity_type.manager -> string_translat  
  ion -> string_translator.locale.lookup -> config.factory -> symfony_mailer.config_override -> plugin.manager.email_builder".  

Patch #45 is working in my case.

Thank you @leewbutler for providing your patch. Having a look at the issue queue I would think this is likely a duplicate of 📌 Automated Drupal 10 compatibility fixes RTBC

RTBC+ (since 2020 in my use case)

@bcobin: Did you already try to clear composer caches after removing drupal/blazy and before re-adding it?
composer cc
You could also run composer diagnose to see if there is a config issue with composer.

In my case: Drupal 9.5.9, PHP 8.1, Composer version 2. When I run composer update I don't use the -w -n options, because I haven't any dev dependencies or scripts in my composer.json.

I solved it by:
composer remove drupal/slick_views

./composer.json has been updated
Running composer update drupal/slick_views
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 0 updates, 3 removals
  - Removing drupal/blazy (2.15.0)
  - Removing drupal/slick (2.8.0)
  - Removing drupal/slick_views (2.6.0)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 0 updates, 3 removals
  - Removing drupal/slick_views (2.6.0)
  - Removing drupal/slick (2.8.0)
  - Removing drupal/blazy (2.15.0)
Deleting web/modules/contrib/slick_views - deleted
Deleting web/modules/contrib/slick - deleted
Deleting web/modules/contrib/blazy - deleted

composer require drupal/slick_views

Using version ^2.6 for drupal/slick_views
./composer.json has been updated
Running composer update drupal/slick_views
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Lock file operations: 3 installs, 0 updates, 0 removals
  - Locking drupal/blazy (2.15.0)
  - Locking drupal/slick (2.8.0)
  - Locking drupal/slick_views (2.6.0)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 3 installs, 0 updates, 0 removals
  - Downloading drupal/blazy (2.15.0)
Gathering patches for root package.
Gathering patches for dependencies. This might take a minute.
  - Installing drupal/blazy (2.15.0): Extracting archive
  - Installing drupal/slick (2.8.0): Extracting archive
  - Installing drupal/slick_views (2.6.0): Extracting archive

This makes absolutely no sense, but it helps.

I can confirm that. In my case running drush cr right after I upgraded from Components 8.x-2.4 to version 3.0.0-beta3 broke the whole site und crashed it's Docker container.

In a second attempt I ran drush updb before clearing the caches. This time I succeeded.

kreatIL → created an issue.

I came across this replacing jquery.cookie by core/js-cookie
In the "after" section there is a typo. Correction:
// Set a cookie.
Cookies.set('cutest', 'red panda');
// Remove a cookie.
Cookies.remove('cutest');
// Retrieve a cookie.
const cutest = Cookies.get('cutest');

@aitala: From your screenshot, one could assume that you ticked "Review Author" before submitting the form. Even if I don't draw that conclusion, I would like to point out that the tick must of course not be set for required fields whose values you don't want to change.

Thank you for investigating in this. I cannot reproduce it anymore on Drupal Version 9.5.2. Closing the issue.

Ok, I tested it again with version 3.26 and can confirm that the error no longer occurs. I should have looked more closely. I am sorry.

I don't see this fixed.

Okay, I went on and created a video explaining a little bit, we can of course document things in details in the future:

This is great, thank you! Your video was of big help for me.

There is one thing I have not yet understood. I had thought that when you create folders in "components", the files they contain are automatically taken into account. I removed the default "block" folder from it and now I get error messages:

ERROR in /components/block/block
Module not found: Error: Can't resolve '/[local_path]/web/themes/custom/pbs5/src/components/block/block.js' in '/[local_path]/web/themes/custom/pbs5'

ERROR in /js/main.script
Module not found: Error: Can't resolve '/[local_path]/web/themes/custom/pbs5/src/components/block/block.scss' in '/[local_path]/web/themes/custom/pbs5'

ERROR in /js/main.script
Module not found: Error: Can't resolve '/[local_path]/web/themes/custom/pbs5/src/js/main.script.js' in '/[local_path]/themes/custom/pbs5'

I have searched all the files of the subtheme for a statement that embeds "block", but have not found any. Where does the error come from?