As a root or reseller users I would like the ability to rename account packages in WHM, preventing the need to create a new package and update account settings with that package.
Renamed a package
Open Discussion
Call for Comments
Currently, there exists no way through the WHM interface to rename a package. Renaming a package would be a very useful feature to have in hosting environments. Architecturally, we would need to supplement the current method of deriving the name of the package from the filename for that package with the ability to specify a new name that can be stored in a parameter within the package file. This new name would be used instead of the filename in displays in the cPanel and WHM interfaces.
Furthermore, for easier package management, the ability to clone/copy an existing package to a new name would be much appreciated.
Original thread: http://forums.cpanel.net/f145/renamed-package-case-53435-a-221912.html
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
Why can't this be implemented by simply renaming the Package file?...instead of introducing 2 names for a Package? (one in the filename {the old name} & another inside the file {the new name})
For example, you create the package "Example_Package", so a file gets created...
/var/cpanel/packages/Example_Package
...with...
Name=Example_Package
...in it...then later, you rename it to "Renamed_Package".
Are you proposing that you end up with a file named...
/var/cpanel/packages/Example_Package
...but now with this content...
Name=Renamed_Package
...I find that to be a horrible solution.
My proposal: The file...
/var/cpanel/packages/Example_Package
...should be renamed to...
/var/cpanel/packages/Renamed_Package
...& any users currently using the old package name would be updated to the new name (by updating that info, wherever it is stored). There would be no need for a "Name=" in the package file at all.
Why can't this be implemented by simply renaming the Package file?...instead of introducing 2 names for a Package? (one in the filename {the old name} & another inside the file {the new name})
For example, you create the package "Example_Package", so a file gets created...
/var/cpanel/packages/Example_Package
...with...
Name=Example_Package
...in it...then later, you rename it to "Renamed_Package".
Are you proposing that you end up with a file named...
/var/cpanel/packages/Example_Package
...but now with this content...
Name=Renamed_Package
...I find that to be a horrible solution.
My proposal: The file...
/var/cpanel/packages/Example_Package
...should be renamed to...
/var/cpanel/packages/Renamed_Package
...& any users currently using the old package name would be updated to the new name (by updating that info, wherever it is stored). There would be no need for a "Name=" in the package file at all.
This request is great. Deriving the package name from the file is a bad idea, the sooner we move to independent package filenames and package names, the better!
This request is great. Deriving the package name from the file is a bad idea, the sooner we move to independent package filenames and package names, the better!
Are there any updates on this?
Are there any updates on this?
No news on this one, I'm sorry. If there is, I'll make sure to let everyone know!
No news on this one, I'm sorry. If there is, I'll make sure to let everyone know!
Replies have been locked on this page!