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

Domain Manager: Support switching registrars for TLD

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.1.0-b2
    • Component/s: None
    • Labels:
      None

      Description

      Currently, it is impossible to switch between registrars for a TLD after services are created. That is far from ideal. We should come up with some way of supporting this.

      The topic could use more thought, but currently this is what I'm thinking.

      Instead of having only one package per TLD, let's keep a list of packages for each tld.

      When the registrar is changed, let's do 1 of 2 things:

      • If a package already exists for this TLD and Registrar, mark that package as active
      • Otherwise create a new package and add it to the list for this TLD. (perhaps we should clone the pricing from the previous package).

      The old package would then be marked "inactive".

      A few database updates will likely be needed.

      • domain_manager_tlds
        • Add id column and make it the primary key
        • Create a unique index on the tld and company columns
        • Change the package_id to active_package_id
      • domain_manager_tld_packages
        • tld_id
        • package_id

      We need to make sure that the TLD list and Modal is base off of the active package from the TLD rather than any of the inactive ones. We'll also need to make sure that the Order form only uses the active package.

        Activity

        Hide
        jonathan Jonathan Reissmueller added a comment -

        The Packages.delete event handler will also need to be updated.

        Show
        jonathan Jonathan Reissmueller added a comment - The Packages.delete event handler will also need to be updated.

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            jonathan Jonathan Reissmueller
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              17/Jun/21

              Time Tracking

              Estimated:
              Original Estimate - 0 minutes
              0m
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 days, 7 hours, 32 minutes
              2d 7h 32m

                Agile