Edit Package should not edit accounts with custom parameters

[JawadArshad]

- When we edit a package in WHM, the changes apply to only the accounts that are created after we edit the package and do not automatically apply to all accounts already on that package.

- This can in theory lead to countless combination of resource limits all using the same package rendering the basic purpose of a package useless. Isn't package supposed to limit resources like disk usage/bandwidth etc to a single limit per package.

- I understand cPanel maintains such limits on a per account basis and any customizations to resource limits would be lost if editing packages is applied to all users on a package, but still most people do not want accounts on a single package to have different limits and it would be hard to manage and organize them. A new package for each resource variation is better to manage rather than editing a package and noting down all accounts created after that for record maintenance and so on.

- cPanel should either implement a way to handle rare customizations differently and force package limits updates across board when we edit a package or
remove 'Edit Package' feature altogether'.
I would request others to comment on this as well and/or correct me if I am wrong.

***For cPanel guys, ticket 547322 as a reference.

[DjiXas]

- When we edit a package in WHM, the changes apply to only the accounts that are created after we edit the package and do not automatically apply to all accounts already on that package.

- This can in theory lead to countless combination of resource limits all using the same package rendering the basic purpose of a package useless. Isn't package supposed to limit resources like disk usage/bandwidth etc to a single limit per package.

- I understand cPanel maintains such limits on a per account basis and any customizations to resource limits would be lost if editing packages is applied to all users on a package, but still most people do not want accounts on a single package to have different limits and it would be hard to manage and organize them. A new package for each resource variation is better to manage rather than editing a package and noting down all accounts created after that for record maintenance and so on.

- cPanel should either implement a way to handle rare customizations differently and force package limits updates across board when we edit a package or
remove 'Edit Package' feature altogether'.
I would request others to comment on this as well and/or correct me if I am wrong.

***For cPanel guys, ticket 547322 as a reference.

Same for "Features", if you transfer account, give him new package, it does not apply default features and uses the ones from server, so you have to change plan few times...

[cPanelDon]

- When we edit a package in WHM, the changes apply to only the accounts that are created after we edit the package and do not automatically apply to all accounts already on that package.

- This can in theory lead to countless combination of resource limits all using the same package rendering the basic purpose of a package useless. Isn't package supposed to limit resources like disk usage/bandwidth etc to a single limit per package.

- I understand cPanel maintains such limits on a per account basis and any customizations to resource limits would be lost if editing packages is applied to all users on a package, but still most people do not want accounts on a single package to have different limits and it would be hard to manage and organize them. A new package for each resource variation is better to manage rather than editing a package and noting down all accounts created after that for record maintenance and so on.

- cPanel should either implement a way to handle rare customizations differently and force package limits updates across board when we edit a package or
remove 'Edit Package' feature altogether'.
I would request others to comment on this as well and/or correct me if I am wrong.

***For cPanel guys, ticket 547322 as a reference.

When editing a disk quota or bandwidth limit in a Package this will trigger an attempt to update existing accounts that have the package assigned to them; however, per further investigation in the ticket the system-specific circumstances lead to certain disk quota modifications taking an extended time to complete and potentially timing-out. The suggested resolution after inspection and per notes from testing was as follows:

WHM: Main >> Server Configuration >> Tweak Settings >> System
Documentation: Tweak Settings

1.) Increase the following time-out threshold beyond the default of 60 seconds:
* Maximum time in seconds that the system is permitted to spend fetching diskusage and quota information before it considers the data unavailable.

2.) Disable the following option:
* Use Safe Quota Setting (quotas will be disabled, adjusted, and then re-enabled). This option should be enabled if you are having problems with lost disk quotas or other quota system corruption. Under software raid and other circumstances enabling this option will degrade server performance.

[cpanelkenneth]

- When we edit a package in WHM, the changes apply to only the accounts that are created after we edit the package and do not automatically apply to all accounts already on that package.

- This can in theory lead to countless combination of resource limits all using the same package rendering the basic purpose of a package useless. Isn't package supposed to limit resources like disk usage/bandwidth etc to a single limit per package.

In general modifying a package should update accounts currently using the package. As Donald notes, the actual display of the change in the product can be impacted by caching.

- I understand cPanel maintains such limits on a per account basis and any customizations to resource limits would be lost if editing packages is applied to all users on a package, but still most people do not want accounts on a single package to have different limits and it would be hard to manage and organize them. A new package for each resource variation is better to manage rather than editing a package and noting down all accounts created after that for record maintenance and so on.

- cPanel should either implement a way to handle rare customizations differently and force package limits updates across board when we edit a package or
remove 'Edit Package' feature altogether'.
I would request others to comment on this as well and/or correct me if I am wrong.

There is discussion on changing the current behavior. One proposal is to remove an account from a package/plan once the account specific details ( e.g. Disk Quota, MAXSQL, etc ) are modified.