@connbi

connbi → created an issue.

I found the issue in the Drupal core issue queue at https://www.drupal.org/project/drupal/issues/3103620 🐛 Dependency on config storage causes circular reference in service container Needs review . Applying the patch fixed the circular reference problem. Thank you for your help! @gausarts

I disabled syslog. then upgrade ultimenu successfully.
Once I enable syslog, this error will occur. @gausarts

Are there any new developments regarding this issue? Or is there a temporary solution to resolve the circular reference?
@gausarts

Based on the error message showing ultimenu.manager -> renderer -> plugin.manager.element_info -> cache_tags.invalidator -> plugin.manager.block, I noticed that renderer is injected in Blazy, which then enters the core cache part of Drupal. I have not yet found the code where cache_tags.invalidator injects into plugin.manager.block. Currently, I can confirm that it should not be related to the reference of plugin.manager.block in UltimenuBase.php, as I commented out that part of the code, and the error still persists.

I checked the service references and found that asset.js.optimizer references logger.channel.default, and the plugin.manager.block in ultimenu.manager also references logger.channel.default. This should be the cause of the circular reference issue.

I suspect this may be related to the simultaneous use of other modules, such as extlink. Of course, this is just my guess and has not been verified yet.

To clarify my situation, I have not previously installed Blazy, and Composer has never installed Blazy either. I only have version 2.10 of Ultimenu.

Unfortunately, I tried the steps you mentioned above, but the error still occurred.

I try to install blazy and then upgrade ultimenu in my site.
my steps as below:

1. drush en blazy -y
2. drush cr
3. composer require 'drupal/ultimenu:^3.0'
4. drush updb
5. drush cr

and then I got error

From the error message, I am also unable to identify which other module is conflicting with ultimenu or blazy.

I'm not sure if I should modify the FieldDiffBuilderInterface like this.
I deleted the mixed return.

New patch for 2.0.0-beta3

$manager = \Drupal::service('ultimenu.manager'); in ultimenu.module 23 line. service create failed.

connbi → created an issue.

I create a patch to revert the code change of css and js asset.

splitTableCellVertically and splitTableCellHorizontally swap places, and change label

I encountered the same problem in drupal 10.3.2. When I accessed the Revision list of a certain taxonomy/taxonomy/term/xxx/revisions, the page reported an error InvalidArgumentException: The timestamp must be numeric.
I created a patch and when the revision created time is empty, I display the changed time of the revision as link text.

In Drupal 10.3.1 same problem exists.
I created a patch to fixed it.

10.3.1 的新补丁
splitTableCellVertically 和 splitTableCellHorizo​​ntally 交换位置

I have the same issue on a multilingual site.
Premise:
Enable multilingual support and workflow on the Drupal site

Using my site as an example,my site includes two languages: Japanese and English.
The steps to reproduce are as follows:

1. Add a Japanese node，save as published
2. Translate the node as English, save as draf, then edit to published
3. Search the EN node

now result：search not found english node
expect result：search can found english node

ConnBi → created an issue.

Is there any plan on when the upgrade path from 2 to 3 will be completed? Very much looking forward to this feat

Fix php warning base on #16

Create a patch for Drupal 10.2.3.

I Create a patch for drupal 10.2.3, And the #107 patch will change the node translation edit link, I revert the code.

ConnBi → created an issue.

move issue to admin toolbar module

ConnBi → created an issue.

Sorry, my patch #6 above replaced one less blockManager variable.
I create a new patch

I created a patch for Drupal 10.2.3

ConnBi → created an issue.

Support Drupal 10.2.3

New patch for 10.2.3
splitTableCellVertically and splitTableCellHorizontally swap places

I have a same problem.
drupal 10.2.3
Ultimenu 2.10
Thanks to @Ibrahim-Tameme, based on your Merge request I created a patch application in ultimenu 2.10 version

I tried to apply all the code modified by MR4713 in drupal 10.1.8 version and found that when selecting "Delete the account and make its content belong to the Anonymous user. This action cannot be undone. Reassign its groups to the super administrator." The created node by this user will also be deleted.Is there any new progress regarding this ticket?

I merged the #45 and #57 patches, create a new patch for Drupal 10.1.4
it's work for me.

Add external uri validate

What is the root cause of this issue, Why is update_default_revision not set to true, causing the translated version to not be deleted?

bijiaxing → created an issue.

I created a new patch for drupal 10.1.4, I agree with @nsciacca, this issue persisted in CKEditor 39.0.1

New patch for 2.0.0-rc7

I re-checked the logic of IEF 2.0.x, I think it's wrong to add validate in canBuild function, the judgement logic should be added to the section of $elements['#multilingual'] = TRUE;
so I create a new patch!

I referred to the code in the PR and created a patch to scan the pictures in the email and replace them with cid. It works normally for me. According to the code in the PR above, there may be a more elegant way to solve it. I don't have time to continue researching this issue at the moment.
my symfony mailer version is 1.2.2. This patch is only used to solve the problem that the embed image is broken in the email body.

Create a patch for 6.2.0-beta6, drupal 10.1.x

#16 the patch is work for me, and the patch which modify the claro.theme is wrong, if user unchecked the Include file in display, the checkbox will always checked.

I have the same problem in IEF 2.0.x and create a new patch for it.

I create a new patch for drupal 10.1.x, thanks for @quadrexdev, the #103 is useful for me. At the same time, I merged the patch in this issue Parent form entity builders run on IEF resulting in fatal errors 🐛 Parent form entity builders run on IEF resulting in fatal errors Active into the new patch.
And I added the code for checking entity langcode and form langcode to get the corresponding entity.

bijiaxing → created an issue.

Create a patch for drupal 10.1.x

New patch for Drupal 10.1.2

bijiaxing → created an issue.

Ploblem still present on D10.1.1 with views_unpublish module.
I create a patch for D10.1.1

Since the new version has not been released. In 9.0.1, this issue is still exist.
I create a patch to fix it.

bijiaxing → created an issue.

When I install pathauto module and not create alias for node, I will got error message:
Deprecated function: str_starts_with(): Passing null to parameter #1 ($haystack) of type string is deprecated in Drupal\path_alias\PathProcessor\AliasPathProcessor->processOutbound() (line 54 of core/modules/path_alias/src/PathProcessor/AliasPathProcessor.php).
Deprecated function: str_starts_with(): Passing null to parameter #1 ($haystack) of type string is deprecated in Drupal\Core\Routing\UrlGenerator->generateFromRoute() (line 309 of core/lib/Drupal/Core/Routing/UrlGenerator.php).
Deprecated function: rawurlencode(): Passing null to parameter #1 ($string) of type string is deprecated in Drupal\Core\Routing\UrlGenerator->generateFromRoute() (line 314 of core/lib/Drupal/Core/Routing/UrlGenerator.php).

bijiaxing → created an issue.

bijiaxing → created an issue.

bijiaxing → created an issue.

Hi kushagra.goyal
I found the same problem, thanks for your new patch.

bijiaxing → created an issue.

bijiaxing → created an issue.

I created a patch to fix this issue.

In 8.x-1.4, not compatibility with drupal 10