Decode HTML entity encoding in the site name before sending data to Payfast. #219
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All Submissions:
Changes proposed in this Pull Request:
The PR addresses the signature mismatch error. Upon investigation, I discovered that the mismatch was due to HTML entity encoding in the site/blog name for special characters. We are sending the blog name in the item name and item description values, and the signature is being generated based on the encoded HTML entity. However, the value in the form is sent with decoded HTML entity, causing the mismatch. This PR resolves the issue by generating the signature based on the decoded HTML entity.
Steps to test the changes in this Pull Request:
Bob's Site
(Please try different combinations).Changelog entry