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

Add option to enable upgrades on package group level

    Details

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

      Description

      It's currently possible for packages to be upgraded to any other package in the same package group that is apart of the same module.

      However, this can pose a problem in some instances. If the module is a domain module, it would not make sense to upgrade to another package, and often other packages in the same group are for separate TLDs, which means the service's domain name would use a package that may no longer support its TLD.

      This task would create a new option for Package Groups to enable/disable package upgrades within the group. It would be checked by default to maintain backward compatibility. If unchecked, no packages within the group can be upgraded, and they should not be listed as options in the admin/client interface.

      See http://www.blesta.com/forums/index.php?/topic/4286-disableremove-change-package-for-domains-in-client-area/

        Activity

        tyson Tyson Phillips (Inactive) created issue -
        tyson Tyson Phillips (Inactive) made changes -
        Field Original Value New Value
        Rank Ranked higher
        tyson Tyson Phillips (Inactive) made changes -
        Story Points 3
        tyson Tyson Phillips (Inactive) made changes -
        Summary Add option to enable upgrades on package group Add option to enable upgrades on package group level
        tyson Tyson Phillips (Inactive) made changes -
        Fix Version/s 3.5.0 [ 10401 ]
        tyson Tyson Phillips (Inactive) made changes -
        Description It's currently possible for packages to be upgraded to any other package in the same package group that is apart of the same module.

        However, this can pose a problem in some instances. If the module is a domain module, it would not make sense to upgrade to another package, and often other packages in the same group are for separate TLDs, which means the service's domain name would use a package that may no longer support its TLD.

        This task would create a new option for Package Groups to enable/disable package upgrades within the group. It would be checked by default to maintain backward compatibility. If unchecked, no packages within the group can be upgraded, and they should not be listed as options in the admin/client interface.
        It's currently possible for packages to be upgraded to any other package in the same package group that is apart of the same module.

        However, this can pose a problem in some instances. If the module is a domain module, it would not make sense to upgrade to another package, and often other packages in the same group are for separate TLDs, which means the service's domain name would use a package that may no longer support its TLD.

        This task would create a new option for Package Groups to enable/disable package upgrades within the group. It would be checked by default to maintain backward compatibility. If unchecked, no packages within the group can be upgraded, and they should not be listed as options in the admin/client interface.

        See http://www.blesta.com/forums/index.php?/topic/4286-disableremove-change-package-for-domains-in-client-area/
        tyson Tyson Phillips (Inactive) made changes -
        Fix Version/s 3.5.0-b2 [ 10701 ]
        tyson Tyson Phillips (Inactive) made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        tyson Tyson Phillips (Inactive) made changes -
        Status Resolved [ 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:
              13/May/15