Updating package not working
Hi I am updating my packages and saw changes are not being reflected, for example I updated the space of a package and saw none emails sent that the packages were updated for the accounts and also if I list the accounts they have the same space (some of the must be over quota) I am suing cloudlinux 8.8 also.
Regards,
-
When you update a package in WHM, you have to then reapply the package to existing users. At least this has been my experience so far. You can do this in mass with the API, for example: for user in `grep PLAN=PackageName /var/cpanel/users/* | cut -d/ -f5 | cut -d: -f1` ; do whmapi1 --output=jsonpretty changepackage user=$user pkg='PackageName' done
Change PackageName to the name of the package, and the above will search for all users using that package and reapply it to them.0 -
@vanessa - interesting - that should *not* be a requirement for editing packages, as any changes should be automatically applied to users with that package immediately. 0 -
I agree, but I just checked on a server running CL8+112 and when I edit the specs of the package, they do not apply to the account until I reapply the package to the account. Possible bug? maybe, but AFAIK it's always behaved this way :) 0 -
Interesting - let me do some testing with this and I'll get back with you! 0 -
Just for clarification, when you say "they don't apply to the account" where specifically are you looking on the system? Somewhere in WHM or cPanel or both? 0 -
So I have an account user1 assigned to a package called "test1" with limited features. When I change the disk quota or set any of the features to "unlimited", I then log into cPanel and see on the right-hand panel showing stats that the features and disk space have not changed. 0 -
I wasn't able to reproduce on a CL8 machine. I created a package, then created an account, logged into cPanel to see the really low disk space I used, then edited the package, then re-logged in to cPanel and I see a really high disk space number. I then repeated the same test with CageFS installed and enabled, and saw the same thing. Could it be browser cache somehow? 0 -
It is a bug in WHM that's existed for over a decade...
Usually, it occurs when packages are over the max account limit in some way, at some point (thus injecting the bug...).
Once the offending package(s) is brought down to reasonable limits well below the max limit, then have the reseller click:
Account Functions -> Upgrade/Downgrade an Account
then reassign the package for the domain in question (after it's been edited to appropriate values of course).
The joys of WHM!0
Please sign in to leave a comment.
Comments
9 comments