@stormy - at this time, no. The only thing I have to offer is to use the API call mentioned on page 1:
Code:
uapi --user=username NVData set names=xmainwelcomedismissed xmainwelcomedismissed=1
You can run that after the account gets created on the server, or you could create a custom hook to add that after account creation so it gets automatically applied to all future accounts that are created on your machine.
@cPRex - I'm not "shooting the messenger" here, so please don't take me the wrong way
Simply put:
A.) It's quicker and easier for us small hosts to log into the customer's cPanel (hopefully before they do) and click "Dismiss"
B.) As can clearly be demonstrated and proven throughout many years of posts on these forums - web hosts do not like executive decisions that take over what our customer's see and experience. It's usually more like "surprise! here's a new
feature that is going to cost you hours of time mitigating while you're trying to just keep up with usual support work".
We've seen these community-wide reactions not only on the recent "Glass" notice to users and the recent "Welcome" notice, but going back through time we can see many instances when unwelcome changes are pushed. Maybe I'm overlooking something, but wouldn't it be wise to simply post a Survey thread here on the forums before implementing new "user experience features" ? Maybe a thread like "Survey - What would you hosts think about this?" with a brief detail of the feature that cPanel is thinking of adding, and then examine the survey results before investing the valuable time of your developers in something that might largely be unwelcome (and could also spare any hurt feelings on the part of the team who came up with the idea / theme / etc... by not having to see the rejection from the community toward something the team probably worked very hard at).
I hope that you'll take this post as constructive and not rude.
As a cPanel customer of over 20 years now practically back to it's infancy, I can honestly say that I think the cPanel staff and developers have done an amazing job over the years and have created an incredible product overall, and that the majority of changes have always been for the better, but there's also been the occasional "new shiny" addition or change that has been met with obvious disenchantment. My hope is that cPanel team & developers will continue to remain encouraged to innovate, but that a balance can be introduced so that important feature requests are addressed as a priority before precious time is put into aesthetics. If anyone were to take a close look at all of the feature requests, a lot of them basically scream "we want the ability to disable / enable any feature, function, icon globally from the Feature Manager, please!". But instead of giving us more control over what the cPanel end-user sees, as we have been asking in many of the feature request threads, what we often get is yet another "feature" that we cannot simply control from the Feature Manager, and ultimately it's counterproductive for everyone involved.
