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

Domain Manager: Seems to add TLDs as "Restricted" Packages.

    Details

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

      Description

      I don't think there's any reason the Domain Manager should create TLDs as "Restricted". To reproduce I did the following:

      1. I added .gr to the Generic Domains module code, this step may not be necessary.
      2. I "Imported" the domain using Generic Domains, which sets no pricing.
      3. I Edit the TLD (Packages > Domain Options) and set a 2 year price.
      4. Somewhere in there, the TLD was either created or updated to be a "Restricted" package, even though it is enabled.

      My understanding is that TLD packages are supposed to be either Active or Inactive, not Restricted.

      1. 1.png
        29 kB
      2. 2.png
        45 kB

        Activity

        Hide
        admin Paul Phillips added a comment -

        Just to note on this one. We use restricted when adding a domain as an admin, especially if something changes like the module. However, if the TLD is "Inactive", it will convert the TLD Package to "Restricted". The TLD was still listed under TLD Pricing as inactive, and when we switched it to "Active", it could not be ordered by normal clients because it was still restricted. This task makes it so that the TLD package gets switched from "Restricted" to "Active" when enabled under TLD Pricing. This way when it appears active, it is actually active and orderable by clients.

        Show
        admin Paul Phillips added a comment - Just to note on this one. We use restricted when adding a domain as an admin, especially if something changes like the module. However, if the TLD is "Inactive", it will convert the TLD Package to "Restricted". The TLD was still listed under TLD Pricing as inactive, and when we switched it to "Active", it could not be ordered by normal clients because it was still restricted. This task makes it so that the TLD package gets switched from "Restricted" to "Active" when enabled under TLD Pricing. This way when it appears active, it is actually active and orderable by clients.

          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:
              17/Apr/25

              Time Tracking

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

                Agile