Prestashop 1.6 #4
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[FIX] Remove commented out sections from previous fix [FIX] Change the way session object is set-up
…not be backwards compatible)
|
This would be interesting to check |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Various changes to get prestapyt working with a modern Requests (2.3.0) and Prestashop 1.6.
NB The change removing urlencoding of POST requests works with Prestashop 1.6.11, but I do not think it is correct. POST requests should be URL encoded. This looks like a workaround for strange behaviour in Prestashop 1.6.
I do not know enough about checking python library numbers, or the current Prestashop API version to make this version work with previous versions of Requests and Prestashop.