CrowMan
07-12-2002, 07:17 PM
Hello all,
Well we pulled deoskins's "Stylus Blue" theme from our server!
The updates were way to slow coming out and the last one did not come out with all the files needed to make the BBS update work.
We are now using Nick's bluelagoon theme. It is very fast and is never out of date. The bluelagoon theme is a light gray color but it works very good. None of our customers requested to be changed back to the "Stylus Blue" theme.
I had big hopes for the Stylus Blue theme but the lack of support killed them!
I will never use another 3rd party theme.
Regards,
Dale Crow
GH1.com
edude
07-12-2002, 07:23 PM
Thanks for this info, i was just about to purchase the stylus blue theme :(
FDrive
07-12-2002, 08:04 PM
We've been using bluelagoon for quite some time now, haven't had a single problem with it yet.
Incognito
07-12-2002, 08:26 PM
The very reason we stick to the standard themes. I believe as web hosts we make more out of wanting to have different themes than our customers do. I continue to follow cpanelgui to see how well they will be maintained and updated. But, frankly, have had no problems or criticisms with the default, iconic, and bluelagoon themes.
edude
07-12-2002, 08:38 PM
I prefer iconic over bluelagoon, whats everyones thoughts?
The Prohacker
07-12-2002, 08:41 PM
I always had to update stylus on the servers, but I love the look so I don't mind doing the updates.....
Although I would like them to update it sometimes :D
StevenG
07-12-2002, 10:02 PM
Blue Lagoon rocks as far as I m concerned.....
akashik
07-13-2002, 12:22 AM
We just use good old iconic. It loads a little better than it used to and customers are used to it. Having said that, a custom panel is in the works though with no ETA.
Greg Moore
edude
07-13-2002, 01:07 AM
custom panel or custom cpanel skin?
Gem Hexen
07-13-2002, 02:04 AM
It is best to stick with the basic CPanel styles, because they are always up to date!
Elena
07-13-2002, 09:48 AM
I'll always stick to the reason why I have my own skin, cpanel releases new features in the default skins that don't work and cause problems. With a custom theme you can first test these things out and then once they work add them in.
For the first time I did something terribly stupid with my skin, I added in 2 new features (the parking features) without testing enough and low and behold I have a bunch of clients who tried it out and now some of their subdomains are stuck (can't be deleted) and I have to manually go in and remove them. Still waiting on a resolution for this bug too.. and yes, the defaults already have these added in. :rolleyes:
So what I'm saying is, sometimes it's not the best thing to have the skins updated immediately. Sure if the updates take too long I would understand the frustration... but how about the frustration the skin designer will go through for adding in new features that don't work and then having hosts complain to them when it is a cpanel mess up?
Matt Lightner
07-14-2002, 04:56 AM
Originally posted by IT Hosting
It is best to stick with the basic CPanel styles, because they are always up to date! That is definitely a benefit. Having to watch the regular themes to maintain a custom theme can get a bit tedious, however as Elena pointed out, it does have its benefits. One of the best is that you know exactly what is in your theme. You won't have to worry about customers writing in about a feature not working, only to discover that you have no idea what that feature is and have never seen it before (sound familiar?). With a custom theme, at least you know exactly what your customers are seeing when they login to their control panel.
Above and beyond that reason, I just think it adds something to a company's image when their control panel is branded with their own company name, information, news, support docs, etc. That's more of a matter of opinion than a logical argument for or against one side though.