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

Require a unique value to be set for configurable options.

        Details

        • Type: Improvement
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: 4.6.0
        • Fix Version/s: 4.7.0
        • Component/s: Staff Interface
        • Labels:
          None

          Description

          When creating a configurable option it's possible to leave the value blank, causing display issues. For example, create a config option drop-down with 2 items where the value is blank. When checking out, only one of the options is displayed because both have the same value of blank.

          • Require a value for config options to be set
          • Require the value to be unique for the config option (can't use the same value for multiple select fields in the same dropdown for example)

            Issue Links

            relates to

            Bug - A problem which impairs or prevents the functions of the product. CORE-3275 Package Option Quantity type may fail to save due to error

            • Major - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. CORE-3525 Add input validation for config option name

            • Major - Major loss of function.
            • Closed

              Activity

              Hide
              Permalink
              tyson Tyson Phillips (Inactive) added a comment -

              It may be that a blank value is desired, but I agree that values should be unique to conform to the form field standards.

              Show
              tyson Tyson Phillips (Inactive) added a comment - It may be that a blank value is desired, but I agree that values should be unique to conform to the form field standards.

                People

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

                  Dates

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

                    Time Tracking

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

                      Agile