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

Import Manager: WHMCS Data too long for column 'summary'

    Details

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

      Description

      tbltickets.title in WHMCS is a text field. support_tickets.summary is varchar 255 in Blesta. An error occurs when a support ticket title/summary in WHMCS is larger than 255 characters.

      [1] => importSupportTickets: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'summary' at row 1 on line 196

      To find these records, we can run this query on the WHMCS database:

      SELECT * FROM tbltickets WHERE (LENGTH(`title`) > '255')

      What we should do in Blesta is truncate tbltickets.title to 255 characters before inserting it into Blesta.

        Activity

        admin Paul Phillips created issue -
        admin Paul Phillips made changes -
        Field Original Value New Value
        Description tbltickets.title in WHMCS is a text field. support_tickets.summary is varchar 255 in Blesta. An error occurs when a support ticket title/summary in WHMCS is larger than 255 characters.

        To find these, we can run this query on the WHMCS database:

        SELECT * FROM tbltickets WHERE (LENGTH(`title`) > '255')

        What we should do in Blesta is truncate tbltickets.title to 255 characters before inserting it into Blesta.
        tbltickets.title in WHMCS is a text field. support_tickets.summary is varchar 255 in Blesta. An error occurs when a support ticket title/summary in WHMCS is larger than 255 characters.

        [1] => importSupportTickets: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'summary' at row 1 on line 196

        To find these records, we can run this query on the WHMCS database:

        SELECT * FROM tbltickets WHERE (LENGTH(`title`) > '255')

        What we should do in Blesta is truncate tbltickets.title to 255 characters before inserting it into Blesta.
        Hide
        admin Paul Phillips added a comment -

        This is also an issue for tblemailtemplates.subject / emails.subject

        Maybe we should truncate many other fields where whmcs uses text and we use varchar

        Show
        admin Paul Phillips added a comment - This is also an issue for tblemailtemplates.subject / emails.subject Maybe we should truncate many other fields where whmcs uses text and we use varchar
        tyson Tyson Phillips (Inactive) made changes -
        Rank Ranked higher
        tyson Tyson Phillips (Inactive) made changes -
        Sprint 4.8.0 Sprint 1 [ 92 ]
        tyson Tyson Phillips (Inactive) made changes -
        Rank Ranked higher
        jonathan Jonathan Reissmueller made changes -
        Assignee Jonathan Reissmueller [ jonathan ]
        Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
        Status Open [ 1 ] In Progress [ 3 ]
        Automated transition triggered when Jonathan Reissmueller created pull request #14 in Stash -
        Status In Progress [ 3 ] In Review [ 5 ]
        Resolution Fixed [ 1 ]
        jonathan Jonathan Reissmueller made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 5 hours, 32 minutes [ 19920 ]
        Worklog Id 12609 [ 12609 ]
        tyson Tyson Phillips (Inactive) made changes -
        Fix Version/s 4.7.1 [ 11126 ]
        Fix Version/s Short Term [ 10800 ]
        Automated transition triggered when Tyson Phillips (Inactive) merged pull request #14 in Stash -
        Status In Review [ 5 ] Closed [ 6 ]

          People

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

            Dates

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

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 5 hours, 32 minutes
              5h 32m

                Agile