Is there an existing issue for this?
Description of problem
The DNN Community Forums module has a legacy name of "Active Forums". As part of our rebranding, we wanted to seamlessly transition to the new name, but the package name has been a roadblock since it is used to bootstrap module upgrades. In particular, if you use the new name as the package name, the installer interprets it as a new install and tries to run all of the previous version's upgrade tasks and scripts. We tried using two different packages, but that was not ideal either.
Description of solution
What we need is to add a "legacyPackageNames" section to the package section. The installer would then use not only the package name to trigger an upgrade, but could use the list in legacyPackageNames as well to determine if the module being installed is actually an upgrade but with a new module name.
<dotnetnuke type="Package" version="5.0">
<packages>
<package name="DNN Community Forums" type="Module" version="09.07.00">
<legacyPackageNames>
<legacyPackageName name="Active Forums" />
</legacyPackageNames>
.
.
.
Description of alternatives considered
No response
Anything else?
No response
Do you plan to contribute code for this enhancement?
Would you be interested in sponsoring this enhancement?
Code of Conduct
Is there an existing issue for this?
Description of problem
The DNN Community Forums module has a legacy name of "Active Forums". As part of our rebranding, we wanted to seamlessly transition to the new name, but the package name has been a roadblock since it is used to bootstrap module upgrades. In particular, if you use the new name as the package name, the installer interprets it as a new install and tries to run all of the previous version's upgrade tasks and scripts. We tried using two different packages, but that was not ideal either.
Description of solution
What we need is to add a "legacyPackageNames" section to the package section. The installer would then use not only the package name to trigger an upgrade, but could use the list in legacyPackageNames as well to determine if the module being installed is actually an upgrade but with a new module name.
<dotnetnuke type="Package" version="5.0"><packages><package name="DNN Community Forums" type="Module" version="09.07.00"><legacyPackageNames><legacyPackageName name="Active Forums" /></legacyPackageNames>...Description of alternatives considered
No response
Anything else?
No response
Do you plan to contribute code for this enhancement?
Would you be interested in sponsoring this enhancement?
Code of Conduct