Never sold reseller accounts until recently so have only just came across this issue, but the core Blesta CPanel module doesn't appear to pass the ACL (Account Creation Limits) onto the account creation, it can create a reseller account according to the package you've assigned it. However the ACL is something that isn't defined by the package and is something I'm having to modify post account creation. These also aren't defined per the ACL Lists but have to be passed to the server on account creation from Blesta. See my screenshot for the values I'm describing, note that these values aren't defined anywhere when creating a package, nor is there any way to edit or set a 'standard value' for these within WHM. These values are set per account and therefore these have to be set at account creation, is there anyway the core module can have this sort of behaviour implemented and what are others doing to overcome this?
The WHM API token has full access.
This was previously brought up here - https://www.blesta.com/forums/index.php?/topic/7417-setting-up-whm-reseller/ but no fix actually provided, instead the poster used CPanel extended which done the job. I don't want to use the third party module, mainly because it keeps being broken, then fixed then broken and would like to stick to the official module.
Question
austenite
Hi there
Never sold reseller accounts until recently so have only just came across this issue, but the core Blesta CPanel module doesn't appear to pass the ACL (Account Creation Limits) onto the account creation, it can create a reseller account according to the package you've assigned it. However the ACL is something that isn't defined by the package and is something I'm having to modify post account creation. These also aren't defined per the ACL Lists but have to be passed to the server on account creation from Blesta. See my screenshot for the values I'm describing, note that these values aren't defined anywhere when creating a package, nor is there any way to edit or set a 'standard value' for these within WHM. These values are set per account and therefore these have to be set at account creation, is there anyway the core module can have this sort of behaviour implemented and what are others doing to overcome this?
The WHM API token has full access.
This was previously brought up here - https://www.blesta.com/forums/index.php?/topic/7417-setting-up-whm-reseller/ but no fix actually provided, instead the poster used CPanel extended which done the job. I don't want to use the third party module, mainly because it keeps being broken, then fixed then broken and would like to stick to the official module.
16 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.