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

Enom: Managing name servers may cause fatal error if only one nameserver is returned by the API

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: 3.6.0
        • Fix Version/s: 4.0.0-b1
        • Component/s: Modules
        • Labels:
          None

          Description

          See http://www.blesta.com/forums/index.php?/topic/5988-enom-module-nameservers/

          A fatal error may be encountered attempting to loop over a single-element non-array. It appears that one nameserver in the response from Enom::manageNameservers is not parsed as a single-element array.

            Activity

            Ascending order - Click to sort in descending order
            tyson Tyson Phillips (Inactive) created issue -
            Automated transition triggered when Tyson Phillips (Inactive) created a branch in Stash -
            Field Original Value New Value
            Status Open [ 1 ] In Progress [ 3 ]
            tyson Tyson Phillips (Inactive) made changes -
            Assignee Tyson Phillips [ tyson ]
            tyson Tyson Phillips (Inactive) made changes -
            Fix Version/s 4.0.0 [ 10603 ]
            Fix Version/s Short Term [ 10800 ]
            Automated transition triggered when Tyson Phillips (Inactive) created pull request #4 in Stash -
            Status In Progress [ 3 ] In Review [ 5 ]
            Resolution Fixed [ 1 ]
            Automated transition triggered when Cody Phillips (Inactive) merged pull request #4 in Stash -
            Status In Review [ 5 ] Closed [ 6 ]

              People

              • Assignee:
                tyson Tyson Phillips (Inactive)
                Reporter:
                tyson Tyson Phillips (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  15/Sep/16