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

Order: Orders can fail to be created due to invalid character serialization from anti-fraud

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.2, 4.2.0-b1
    • Component/s: Plugins
    • Labels:
      None

      Description

      It's possible for an order record to fail to be created despite the creation of a service/invoice during checkout. The customer is then redirected to the beginning of the order process.

      This issue occurs due to the serialization of unicode characters (e.g. é) that are not properly encoded from a Fraud Report using one of the anti-fraud modules. This was encountered on MaxMind in particular, but all modules (i.e. FraudsLab) should also be updated with a fix.

      TODO:

      1. Update MaxMind and FraudsLabPro anti-fraud modules to ensure the fraud details are UTF8-encoded. !!Test!!
      2. Remove serialization in favor of JSON-encoding the data. ENSURE BACKWARD COMPATIBILITY

        Activity

        tyson Tyson Phillips (Inactive) created issue -
        tyson Tyson Phillips (Inactive) made changes -
        Field Original Value New Value
        Sprint 4.2.0 Sprint 1 [ 46 ]
        tyson Tyson Phillips (Inactive) made changes -
        Rank Ranked higher
        tyson Tyson Phillips (Inactive) made changes -
        Rank Ranked higher
        tyson Tyson Phillips (Inactive) made changes -
        Rank Ranked higher
        Automated transition triggered when Tyson Phillips (Inactive) created a branch in Stash -
        Status Open [ 1 ] In Progress [ 3 ]
        tyson Tyson Phillips (Inactive) made changes -
        Description It's possible for an order record to fail to be created despite the creation of a service/invoice during checkout. The customer is then redirected to the beginning of the order process.

        This issue occurs due to the serialization of unicode characters (e.g. é) that are not properly encoded from a Fraud Report using one of the anti-fraud modules. This was encountered on MaxMind in particular, but all modules (i.e. FraudsLab) should also be updated with a fix.

        TODO:
        # Update MaxMind and FraudsLabPro anti-fraud modules to ensure the fraud details are UTF8-encoded. *!!Test!!*
        # Remove serialization in favor of JSON-encoding the data. *!!ENSURE BACKWARD COMPATIBILITY!!*
        It's possible for an order record to fail to be created despite the creation of a service/invoice during checkout. The customer is then redirected to the beginning of the order process.

        This issue occurs due to the serialization of unicode characters (e.g. é) that are not properly encoded from a Fraud Report using one of the anti-fraud modules. This was encountered on MaxMind in particular, but all modules (i.e. FraudsLab) should also be updated with a fix.

        TODO:
        # Update MaxMind and FraudsLabPro anti-fraud modules to ensure the fraud details are UTF8-encoded. *!!Test!!*
        # Remove serialization in favor of JSON-encoding the data. *ENSURE BACKWARD COMPATIBILITY*
        Automated transition triggered when Tyson Phillips (Inactive) created pull request #29 in Stash -
        Status In Progress [ 3 ] In Review [ 5 ]
        Resolution Fixed [ 1 ]
        tyson Tyson Phillips (Inactive) made changes -
        Assignee Jonathan Reissmueller [ jonathan ] Tyson Phillips [ tyson ]
        tyson Tyson Phillips (Inactive) made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 2 hours, 25 minutes [ 8700 ]
        Worklog Id 10311 [ 10311 ]
        Automated transition triggered when Tyson Phillips (Inactive) merged pull request #29 in Stash -
        Status In Review [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            tyson Tyson Phillips (Inactive)
            Reporter:
            tyson Tyson Phillips (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              25/Oct/17

              Time Tracking

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

                Agile