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

Service validation should check quantity is 1 or more

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: 3.1.0-b1
        • Fix Version/s: 3.2.0
        • Component/s: None
        • Labels:
          None

          Description

          When a service is added, a quantity of 0 can be entered, (e.g. for universal module service options), and when added through checkout, is converted to a quantity of 1. Instead, an error should be displayed that the quantity should be 1+.

            Issue Links

            relates to

            Bug - A problem which impairs or prevents the functions of the product. CORE-1121 Configurable options of quantity 0 can be ordered

            • Critical - Crashes, loss of data, severe memory leak.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. CORE-1145 Check quantity availability when validating module fields of service

            • Major - Major loss of function.
            • Closed

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              cody Cody Phillips (Inactive) added a comment - - edited

              This issue appears to request that:

              1. Services with quantity 0 not appear in the Order plugin checkout process
              2. Service options with quantity 0 not appear in the Order plugin checkout process

              The above can't be handled gracefully in the Order plugin because it must support display items in the order summary (that may not necessarily be in the cart). For example:

              1. User loads AJAX slider order form
              2. Default package has blank quantity field (quantity is zero)

              The above requirements insist that any service with quantity zero not appear in the summary. This would prevent that item's configurable options from being shown in the order summary as well. I don't believe that is the desired behavior.

              According to CORE-1121, any service with quantity of 0 will result in error when adding, so checkout is blocked.

              So, what, exactly, is the purpose and goal of not allowing items with 0 quantity through the Order plugin?

              Show
              cody Cody Phillips (Inactive) added a comment - - edited This issue appears to request that: Services with quantity 0 not appear in the Order plugin checkout process Service options with quantity 0 not appear in the Order plugin checkout process The above can't be handled gracefully in the Order plugin because it must support display items in the order summary (that may not necessarily be in the cart). For example: User loads AJAX slider order form Default package has blank quantity field (quantity is zero) The above requirements insist that any service with quantity zero not appear in the summary. This would prevent that item's configurable options from being shown in the order summary as well. I don't believe that is the desired behavior. According to CORE-1121 , any service with quantity of 0 will result in error when adding, so checkout is blocked. So, what, exactly, is the purpose and goal of not allowing items with 0 quantity through the Order plugin?
              Hide
              Permalink
              admin Paul Phillips added a comment -

              This would apply only to configurable options, not to packages with a quantity of 0.

              Show
              admin Paul Phillips added a comment - This would apply only to configurable options, not to packages with a quantity of 0.

                People

                • Assignee:
                  cody Cody Phillips (Inactive)
                  Reporter:
                  tyson Tyson Phillips (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    14/May/14