I don't mind using my own skins. All my hosting plans use my custom ones because I have full control of the features and the layout.
I voted yes though because it would be a nice feature. It would make it so much easier for others who don't want to make and keep up to date, their own skins.
I voted yes though because it would be a nice feature. It would make it so much easier for others who don't want to make and keep up to date, their own skins.
That's very timeconsuming when you want to create specific skins for different type of customers.
I would like to be able to disable/enable specific features for certain customers without having to create another hosting package and clone another skin for them.
I would end up with a dozen of clones and having to update them as well!
Also I would like to create several different hosting packages, for example an 'e-commerce' package, where I would enable OSCommerce, and disable most of the other irrelevant scripts.
The cloning method is very unpractical.
A big, resounding, YES!
I would presume that DarkOrb already has something in the works and is diligently testing/troubleshooting such a great option. May sound easy to implement, but only a programmer would know the problems involved with this type of feature.
Even though it would be nice feature to have 'now', there are more important ones that need to be corrected/altered before bringing in a new one like this.
I would presume that DarkOrb already has something in the works and is diligently testing/troubleshooting such a great option. May sound easy to implement, but only a programmer would know the problems involved with this type of feature.
Even though it would be nice feature to have 'now', there are more important ones that need to be corrected/altered before bringing in a new one like this.
Yes I know of Rvskin, but in my opinion the disabling/enabling should be implemented in CPanel, so you can use it with all the skins.
If possible I would prefer not to be dependent on a 3rd party skin for this feature.
As far as complexity, I don't see what the complexity could be. You just generate the skins based on the options selected. Just like the method they used for setting up resellers.
Ofcourse this is not a priority, there are more important issues to attend to at the moment, but I would like to have this feature at some point in the future.
I did submit this feature request back in December already also.