When creating a package for ModernBill/Cpanel combination, is it better to utilize the WHM packages feature or is it better to explicitly define the package specs in MB?

Thanks!

Good question, that was something I needed to research but a local network buildout distracted me.

I believe if you use the packages in WHM then you dont need to define the cpanel attributes in MB, or you can define the cpanel attributes in MB, and nevermind the WHM package field.

In fact I believe what I just typed is correct if I remember correctly, if you do both and there is a discrepancy it can conflict, but it wont error, it will "By chance" use one set of attributes or the other. Which makes sense really, its like a random thing =) which may answewr your question partly, its a matter of personal choice I thinik, define the cpanel attributes in WHM, OR MB

Yes.

See, I'm wondering if there are "other" factors to consider with this decision.

ie: If you don't use the WHM packages feature, then it limits some rvskin functionality, etc...

There may be a number of "unseen" repercussions to using the MB "custom package" ability instead of the WHM package ability.

I was just wondering if anyone who is operating with MB for a while now (and cpanel) might have some experience they would be willing to share.

Thanks!

Hi,

I would also like to know the answer to this as I'm performing a Modernbill installation this week, so it will be good to know.

I think it might be best to use WHM's built in features, just in case..

Originally posted by mrzippy
If you don't use the WHM packages feature, then it limits some rvskin functionality
In what way does it limit rvskin functionality?