🇨🇦Canada @adriancid

After this command:

- composer require 'drupal/node_revision_delete:^2.0@RC'

You need to clear the cache:

- drush cr

- composer require 'drupal/node_revision_delete:^1.0@RC'
- drush pmu -y node_revision_generate
- drush cex
- composer require 'drupal/node_revision_delete:^2.0@RC'

The node revision generate module is just for test pourpose, so this module don;t made nothing in your site other than generate revisions to test the node revision generate module, it was removed on the latest version.

You can do the following

- composer require 'drupal/node_revision_delete:^1.0@RC'
- uninstall the module
- export the configs
- composer require 'drupal/node_revision_delete:^2.0@RC'

Thanks

DamienMcKenna → credited adriancid → .

Can you add steps to reproduce the problem?

adriancid → created an issue.

Thanks

adriancid → created an issue.

adriancid → created an issue.

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

D8 is deprecated and D9 too, so D10 version is out.

adriancid → created an issue.

Thanks, I changed to branch 2.x because we had the 8.x-1.x

adriancid → created an issue.

Closing because we have a working patch in ✨ Log revision deletion Needs work and I will give credit there

Closing because the current development is being made in branch 2.x

Closing because the current development is being made in branch 2.x

Closing because the current development is being made in branch 2.x

Closing because the current development is being made in branch 2.x

Closing because the current development is being made in branch 2.x

Closing because the current development is being made in branch 2.x

Closing because the current development is being made in branch 2.x

arriving soon to the 10 anniversary :-D, let's see if this ticket is fixed someday.

Closing because the current development is being made in branch 2.x

Closing because the current development is being made in branch 2.x

Closing because the current development is being made in branch 2.x

Closing because the current development is being made in branch 2.x, and I don't see this error there.

Closing because the current development is being made in branch 2.x

adriancid → created an issue.

adriancid → created an issue.

Closing because the current development is being made in branch 2.x

Closing because the current development is being made in branch 2.x

Closing because the current development is being made in branch 2.x

Closing because the current development is being made in branch 2.x

Thanks

Thanks

adriancid → created an issue.

Thanks to all the contributors.

The release is ready: https://www.drupal.org/project/form_mode_manager/releases/3.0.0 →

I tried to merge but the pipeline failed

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

When I merged the master branch into this branch 1 test failed in the pipeline.

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

I think we should handle this in two ways, because why we need a hook_unistall when you can enforce in the configuration files the removal of the configs?

So what I'm proposing is handle here the uninstall of the existing configurations if the module is installed using a hook_update. We should add to the configurations the dependency, and in 📌 Enforce the configurations to be uninstalled at the same time as the example module Active enforce the configurations to be uninstalled once the module is uninstalled from the site.

adriancid → created an issue. See original summary → .

@Summit yes, but you can go and use the new release for Modules Weight module too if you need to change the weight.