Details
-
Type: Bug
-
Status: Closed
-
Priority: Minor
-
Resolution: Won't Fix
-
Affects Version/s: 3.1.1
-
Fix Version/s: 3.2.1
-
Component/s: None
-
Labels:None
Description
See http://www.blesta.com/forums/index.php?/topic/2033-error-of-adding-number-to-client-via-mozilla/
When you attempt to add multiple phone numbers when editing a client, posting that data can result in an error:
SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'type' cannot be null on line 124 in /var/www/vhosts/my.blesta.site/public_html/lib/model.php
This appears to only happen when:
1. You already have a phone number of Type "Phone" or Location "Home" (i.e. the default values when you click Add Additional Number)
and
2. You try to add an additional phone number that uses one of the default type/location values of "Phone" or "Home". and you did not change the value in either of those drop-downs from their default value of Phone/Home
The result is then that Firefox does not post the cloned field for Type/Location if the user did not change the value in the drop-down.
The issue may be related to Firefox/jquery or some of the javascript that clones fields in the DOM when clicking to add another phone number such that the field is not set in Firefox until it's value has been updated.
Activity
Field | Original Value | New Value |
---|---|---|
Description |
See http://www.blesta.com/forums/index.php?/topic/2033-error-of-adding-number-to-client-via-mozilla/
When you attempt to add multiple phone numbers when editing a client, posting that data can result in an error: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'type' cannot be null on line 124 in /var/www/vhosts/my.blesta.site/public_html/lib/model.php This appears to only happen when: 1. You already have a phone number of Type "Phone" or Location "Home" (i.e. the default values when you click Add Additional Number) -and- 2. You try to add an additional phone number that uses one of the default type/location values of "Phone" or "Home". -and- *important* you did not change the value in either of those drop-downs from their default value of Phone/Home The result is then that Firefox does not post the cloned field for Type/Location if the user did not change the value in the drop-down. The issue may be related to Firefox/jquery or some of the javascript that clones fields in the DOM when clicking to add another phone number such that the field is not set in Firefox until it's value has been updated. |
See http://www.blesta.com/forums/index.php?/topic/2033-error-of-adding-number-to-client-via-mozilla/
When you attempt to add multiple phone numbers when editing a client, posting that data can result in an error: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'type' cannot be null on line 124 in /var/www/vhosts/my.blesta.site/public_html/lib/model.php This appears to only happen when: 1. You already have a phone number of Type "Phone" or Location "Home" (i.e. the default values when you click Add Additional Number) -and- 2. You try to add an additional phone number that uses one of the default type/location values of "Phone" or "Home". *and* you did not change the value in either of those drop-downs from their default value of Phone/Home The result is then that Firefox does not post the cloned field for Type/Location if the user did not change the value in the drop-down. The issue may be related to Firefox/jquery or some of the javascript that clones fields in the DOM when clicking to add another phone number such that the field is not set in Firefox until it's value has been updated. |
Summary | Unable to add multiple phone numbers of the same type and location in Firefox | Unable to add multiple client phone numbers of the same type/location in Firefox |
Summary | Unable to add multiple client phone numbers of the same type/location in Firefox | Unable to add multiple client phone numbers of the same type/location through Firefox |
Fix Version/s | 3.1.4 [ 10500 ] | |
Fix Version/s | 3.1.3 [ 10405 ] |
Fix Version/s | 3.2.1 [ 10504 ] | |
Fix Version/s | 3.1.4 [ 10500 ] |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Won't Fix [ 2 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
This issue does not affect Firefox 29, and was likely fixed in version 28 or 29.