Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.5.0-b2
-
Component/s: None
-
Labels:None
Description
This issue comes up a lot with WHMCS imports. Some special characters will come from an imported database in a format/encoding that is not recognized by Blesta. When we attempt to store this in the database, exceptions are thrown and the import fails.
In the WHMCS importer we fixed this by applying a decode() method to most every string pulled from the database, which decodes the string and then encodes it for the Blesta database.
Some importation is handles by the parent Migrator class. Either this class should be updated to decode data in a similar way, or the WHMCS migrator should be updated to override the parent functions and do it's own importation and decoding. Testing will need to be done to see if adding such code to the parent class would cause issues with the other migrators.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
This issue come up a lot with WHMCS imports. Some special characters will come from an imported database in a format/encoding that is not recognized by Blesta. When we attempt to store this in the database, exceptions are thrown and the import fails.
In the WHMCS importer we fixed this by applying a decode() method to most every string pulled from the database, which decodes the string and then encodes it for the Blesta database. Some importation is handles by the parent Migrator class. Either this class should be updated to decode data in a similar way, or the WHMCS migrator should be updated to override the parent functions and do it's own importation and decoding. Testing will need to be done to see if adding such code to the parent class would cause issues with the other migrators. |
This issue comes up a lot with WHMCS imports. Some special characters will come from an imported database in a format/encoding that is not recognized by Blesta. When we attempt to store this in the database, exceptions are thrown and the import fails.
In the WHMCS importer we fixed this by applying a decode() method to most every string pulled from the database, which decodes the string and then encodes it for the Blesta database. Some importation is handles by the parent Migrator class. Either this class should be updated to decode data in a similar way, or the WHMCS migrator should be updated to override the parent functions and do it's own importation and decoding. Testing will need to be done to see if adding such code to the parent class would cause issues with the other migrators. |
Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Tyson Phillips (Inactive)
made changes -
| Sprint | 4.6.0 Sprint 1 [ 68 ] |
Tyson Phillips (Inactive)
made changes -
| Rank | Ranked higher |
Tyson Phillips (Inactive)
made changes -
| Rank | Ranked higher |
Tyson Phillips (Inactive)
made changes -
| Rank | Ranked lower |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 2 hours, 12 minutes [ 7920 ] | |
| Worklog Id | 11948 [ 11948 ] |
Automated transition triggered when Jonathan Reissmueller created pull request #12 in Stash -
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Time Spent | 2 hours, 12 minutes [ 7920 ] | 3 hours, 19 minutes [ 11940 ] |
| Worklog Id | 11951 [ 11951 ] |
Automated transition triggered when Tyson Phillips (Inactive) merged pull request #12 in Stash -
| Status | In Review [ 5 ] | Closed [ 6 ] |
