I’m not sure why, but if I go into a Module Package and rename it then save, deploy, the Module’s previous name remains in Studio as its own module alongside the Renamed Module. I can’t figure out why this is happening or how to get it to remove the previous name module as it doesn’t appear in Module Package.
Have you tried Quick Repair & Rebuild(QR&R)?
Admin → Repair → QR&R
I have tried QRR but unfortunately it did not fix the issue. As the suite we use is shared with several other organisations, I am hesitant to take any action which could affect them.
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):
- You’ve build module A in the builder and deployed it
- You’ve renamed A into B in the builder (which is an installed instance / copy of your module)
- 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.