Problem/Motivation

The name of the module folder is not the same as the machine name of the configuration files.

CommentFileSizeAuthor
#2 my-changes.patch0 bytesniharika.s
Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

iván barrios created an issue. See original summary.

niharika.s’s picture

Status: Active » Needs review
StatusFileSize
new0 bytes

I have applied the changes by renaming the folder name , please review .

omarlopesino’s picture

Patch from #2 is empty. Is it possible that you have renamed it but the patch haven't been generated correctly?

I suggest you following these instructions or use Drupal GItalb repositories to create a merge request.

omarlopesino’s picture

About this issue, I am aware of this problem, and we have this important problem if we fix it: If we release a new version changing the module name, the sites using this module would break. It is true that uninstalling the site , updating the module, and reinstalling it would fix it, but having to reconfigure an entire module should be avoided. Any ideas to deal with this problem?