Fixing Magento Invalid attribute name issue after SUPEE-11219 #887
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
Removed 2nd if check after M version upgrade broke this for many grids Described here https://www.garybell.co.uk/fix-magento-invalid-attribute-error-supee-11219/ and here https://magento.stackexchange.com/a/292307/78
colinmollenhour approved these changes Jan 20, 2020
Contributor
| I'd like to close .... https://magento.stackexchange.com/questions/292092/supee-11219-potential-issues/292307#292307
Just put callback into right class. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 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.
Removed 2nd if check after M version upgrade broke this for many grids
Described here
https://www.garybell.co.uk/fix-magento-invalid-attribute-error-supee-11219/
and here https://magento.stackexchange.com/a/292307/78
Fixes #882