🇯🇵Japan @s-jack

s-jack → created an issue.

s-jack → created an issue.

This may be an off-topic question, but I'm sorry.

I followed the advice.
composer require "drupal/jquery_ui_accordion:^2.1"

I have not installed the jquery_ui_accordion module by UI or Drush.
I just imported it with Composer.
As a test, I tried updating the database without installing it.
The database update that was causing the problem was successful.

I have a question, but will the module be automatically installed when I update the database?

The jquery_ui module and several related modules are used, such as better_exposed_filters and the taxonomy_manager module.

I have encountered a similar case.
This is on a site installed from Drupal 10.
I am not using the accordion type.

Why do I have to install jquery_ui_accordion once?

In an era where we are updating towards Drupal 11 without using Composer manually, having to do this manually would be a huge hindrance.

I also don't know how to find the format_type: accordion configuration, as I am not a developer.

Thanks for the field group module.

s-jack → created an issue.

Hi sathishdevan and sayco.

I had not yet applied the patch to check it, but once I placed the field in the paragraph type and immediately removed it, I confirmed that the module can be uninstalled.
Thank you for pushing the patch.

With the modification of #2 comment, it seems to be working fine.
Thank you.

Hi sathishdevan.

I am a user with a level of interest in basic programming, so I do not understand the detailed specifications.

I assume that fields are reusable when they are placed in concrete bundles.
But are you saying that the fields in this module are created internally without placing them in a bundle?

If so, then the fact that fields cannot be deleted is a specification and not a bug.
However, from the user's perspective, it is very inconvenient to not be able to uninstall without special work.

What exactly do you mean by "if you create a path to delete a field?"

Created a new clean site test environment.
Installed only Paragraphs 8.x-1.17 and Paragraph View Mode 3.1.3 modules.
I did not create any content using paragraphs or paragraph types, only modules were installed.
The Paragraph View Mode module cannot be uninstalled.
Therefore, the module also cannot be uninstalled due to dependencies.

Uninstalled and verified the modules related to paragraphs.

1. Paragraphs Editor Enhancements module uninstalled.
2. The Paragraphs Features module was uninstalled.

To my surprise, the remaining two Paragraphs and Paragraph View Mode modules are interdependent and neither can be removed.

This seems to be a bug.

Just to be sure, the following tasks were verified.

1. Tried to delete all content that uses paragraphs, but the fields cannot be deleted and the module cannot be uninstalled.
2. Tried to delete all content types that use paragraph types, but the fields cannot be deleted and the module cannot be uninstalled.
3. Tried to delete all paragraph types, but fields cannot be deleted and the module cannot be uninstalled.

It is odd that the module cannot be uninstalled because the field is assumed to be in use, even though everything using the paragraph has been removed.

Is the only possibility left to remove the other paragraph-related modules themselves?

s-jack → created an issue.

Hi, @ravi kant.
Before I do that, I am trying to upgrade drupal 8.x to 9.x but I am hitting a wall.
It is Composer spaghetti.
Hence, I cannot upgrade the Rate module.

Anyway, after downgrading to version 6.0.8, which is one version lower, the error disappeared.

Thank you for comment.
I forgot to tell you my Drupal environment is 8.9.20.
I think Webform 6.1.4 is the latest for Drupal 8.9.20.

As a side note, I am having trouble upgrading to Drupal 9 because I used pantheon-systems/example-drops-8-composer first.

s-jack → created an issue.