Updating Module Package Name creates second Module in Studio? Why?

English Language - Forum
4

I’ve had sth. similar and I only got things removed by going into the DB.

What happens there (I assume - not sure about the code specifics or your process):

  1. You’ve build module A in the builder and deployed it
  2. You’ve renamed A into B in the builder (which is an installed instance / copy of your module)
  3. You’ve deployed module B (without uninstalling module A first)

You should have the two different packages now showing in the module loader.
Theoretically, you can now uninstall module A and keep B (most likely, the data will be lost if there is any in module A).

Additionally, you’d do all of this first on a dev environment, with a backup before - so you don’t have to worry about any live processes.

1 Like