How can we improve WHMCS?

Share, discuss and vote for what you would like to see added to WHMCS

Change the dedicated servers/VPS order for NS and hostname

  • Anonymous shared this idea 10 years ago
  • Order Forms
  • 3 Comments


In the product group you can choose VPS/Dedicated server group when adding a product, by doing this the order form will reflect:

Hostname:

NS1:

NS2:

root pass:

Which is all good.

The issue is when a user fills this information in and places the order
the fields Hostname:, NS1:, NS2: all duplicate the information.

Example

Hostname: server.something.com

NS1: NS1.something.com

NS2: NS2.something.com

Place the order and the backend results are:

Hostname: server.something.com.something.com

NS1: NS1.something.com.something.com

NS2: NS2.something.com.something.com

A simple remedy would be to limit the NS prefix field to 4 so NS1 or DNS1

Or to better explain what the user should do and have text already in the field showing as an example.

3 Comments

Login to post a comment.

  • <div class="fields-container">
  • [co]
  • <div class="field-row clearfix">
  • <div class="col-sm-4">{$LANG.serverhostname}</div>
  • <div class="col-sm-8 row">
  • <div class="col-xs-4">
  • <input type="text" name="hostname" value="{$server.hostname}" placeholder="servername.yourdomain.com" class="form-control" />
  • </div>
  • <div class="col-xs-8">
  • <p class="form-control-static"></p>
  • </div>
  • </div>
  • </div>
  • <input type="hidden" name="ns1prefix" value="ns1" />
  • <input type="hidden" name="ns2prefix" value="ns2" />
  • <input type="hidden" name="rootpw" value="your root password"/>
  • </div>
  • [/co]
    Is that really "in progress" ?

    Because I'd like to ask you to consider allowing admins to hide those fields. They are useless in a lot of situations.

    Mostly only confuses less experient buyers.
    Hi,
    Thanks for taking the time to provide your feedback. This situation can arise when ordering a dedicated server product whilst the "Require Domain" option is ticked in the product configuration. This is an atypical configuration, that said we appreciate it is a entirely possible configuration. Case #CORE-9759 is open internally with our development team to prevent the domain field from being double-populated in a future release.
    In the meantime, the workaround is to UNtick the "Require Domain" checkbox in the product configuration.