Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-3430

cPanel: Domain not auto-populated in order form

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.8.1
    • Component/s: None
    • Labels:
      None

      Description

      When creating a service through the domain type order form we allow modules to default their domain field to the value of the domain that was previously checked and selected. As of 4.8 cPanel stopped doing this. See getClientAddFields()

        Activity

        Hide
        tyson Tyson Phillips (Inactive) added a comment -

        Does this need to be done for the "cpanel_domain" fields for both subdomains and for both client and admin fields from getClientAddFields/getAdminAddFields?

        Show
        tyson Tyson Phillips (Inactive) added a comment - Does this need to be done for the "cpanel_domain" fields for both subdomains and for both client and admin fields from getClientAddFields/getAdminAddFields ?
        Hide
        jonathan Jonathan Reissmueller added a comment -

        Not exactly. So the method should be update to use $vars->domain as a backup default value. That value is only populated in the order form, so the admin change would not be useful. You could populate the subdomain field, but the validated domain would have been a full domain, so it might be odd to populate it with that value.

        Show
        jonathan Jonathan Reissmueller added a comment - Not exactly. So the method should be update to use $vars->domain as a backup default value. That value is only populated in the order form, so the admin change would not be useful. You could populate the subdomain field, but the validated domain would have been a full domain, so it might be odd to populate it with that value.

          People

          • Assignee:
            jonathan Jonathan Reissmueller
            Reporter:
            jonathan Jonathan Reissmueller
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              11/Feb/20

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 10 minutes
              10m

                Agile