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

Inactive packages shown but not accepted in admin interface

    Details

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

      Description

      When creating a service for a client as an admin, we list Inactive and Restricted packages. Restricted packages are disabled options unless the client has access to them. However, Inactive packages are selectable options even though they are not intended to be used. Attempting to create a service from an inactive package leads to the following error:

      The client can not access that package.

      1. Update the package list when adding a service to disable inactive packages, similar to restricted packages

      When adding a service through the admin interface, inactive packages are shown among the package options. However, after selecting that package and attempting to add the service, an error is encountered saying "The client can not access that package". We should either modify this to accept inactive packages or otherwise not list them. Probably the latter.

        Activity

          People

          • Assignee:
            jonathan Jonathan Reissmueller
            Reporter:
            jonathan Jonathan Reissmueller
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              5/Sep/19

              Time Tracking

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

                Agile