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

Domains: When importing TLDs, if a TLD fails it is still created with 0.00 pricing

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.9.0-b1
    • Fix Version/s: 5.9.0-b2
    • Component/s: Plugins, Staff Interface
    • Labels:
      None

      Description

      When importing TLDs using a registrar, like OpenSRS, some may fail and some may succeed. If any fail, the TLDs are still created in Blesta but their prices are set to 0.00. If importing a TLD fails to fetch pricing from the registrar, do not create the TLD in Blesta.

      I was able to reproduce this by using OpenSRS and importing the TLDs .sh, and .xyz. .sh was successful, while .xyz failed.

      The request for .xyz failed with this response:

      INPUT:
      https://horizon.opensrs.net:55443
      a:4:

      {s:6:"domain";s:30:"tldpricingtestdomainblesta.xyz";s:6:"period";i:1;s:11:"all_periods";i:1;s:8:"reg_type";s:3:"new";}

      OUTPUT:
      https://horizon.opensrs.net:55443
      <?xml version='1.0' encoding="UTF-8" standalone="no" ?>
      <!DOCTYPE OPS_envelope SYSTEM "ops.dtd">
      <OPS_envelope>
      <header>
      <version>0.9</version>
      </header>
      <body>
      <data_block>
      <dt_assoc>
      <item key="object">DOMAIN</item>
      <item key="is_success">0</item>
      <item key="protocol">XCP</item>
      <item key="response_text">No registry agent to service .xyz</item>
      <item key="action">REPLY</item>
      <item key="response_code">400</item>
      </dt_assoc>
      </data_block>
      </body>
      </OPS_envelope>

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              5/Jan/24

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 hours, 42 minutes
              2h 42m

                Agile