> I agree, it's not the smoothest method - but during development we were also
> under incredible time pressures due to registry timelines, and lack of
> registry information up front about required fields (etc). That piece was
> simply forgotten; however, not to say we WONT put it in - it's just not
> there.
>
> We hear your pleas :) I'll see if we can't get this in for the next release
> (not the one this weekend, but the next one - shouldn't be too long
> afterwards).
>
I'm glad that you at least realized those problems :-) In my opinion it would
be quite simple to overcome all those and future problems if you would offer
the option to automatically add a new or transferred domain to a given
profile, a "default profile". This profile could be configured via RWI and
stored in your database and apply to the RWI *and* the client code. And on the
registration form I just click a checkbox "manage with default profile" to get
it automatically saved to this profile. To further ease this you could
implement that this "default profile" can be managed with our reseller
user/password instead of domain/user/password. This would spare us a *lot* of
time and would completely eliminate "loading profiles" - at least for us.
This would also eliminate any problems with mistyped or forgotten profile
combinations. Last week I wasn't able to manage one of our domains because it
was accidentally submitted with *one* character missing off the username when
we transferred it. I had to send me the password info via email. Imagine I had
used the client's email address as the admin contact email and it wouldn't be
valid anymore (which frequently happens with clients). In my eyes, this "three
word combination" system *invites* for problems because of typos and forgotten
data.
Thanks for listening :-)
Kai
--
Kai Sch�tzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
IE-Center: http://ie5.de & http://msie.winware.org
ClubWin - Help for Windows Users: http://www.clubwin.com
