Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.1.0, 3.2.0, 3.3.0, 3.4.0, 3.5.0
-
Fix Version/s: 3.5.1
-
Component/s: None
-
Labels:None
Description
Web browsers don't decode POSTed select option values, which is causing a comparison of an HTML encoded and HTML decoded version of a package option value when a service is being created, resulting in an error because the package option value could not be found.
There are a couple ways to resolve it, e.g.:
1. Decode the select value whenever it needs to be used after POSTed from the browser. This can be difficult is it can effect multiple areas of the system, and requires knowledge of the type of input field each value came from.
2. Disallow config options of the "Drop-down" type from being able to define characters in an option value that are not identical to their HTML encoded equivalent. This is a much simpler solution (i.e. show an error message), but it limits the characters you can set as a drop-down value, which can have negative implications if you require those special characters.
#2 may be the best option at this time
See http://www.blesta.com/forums/index.php?/topic/4765-configurable-options/
Activity
Tyson Phillips (Inactive)
created issue -
Tyson Phillips (Inactive)
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Tyson Phillips (Inactive)
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |