-
-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG SUPEE-11219 – Wrong Field Specified error in 1.9.x - needs a fix #1145
Comments
On a freshly installed OpenMage LTS 19.4.9 test site, when I try and save shipment methods, I get the aforementioned error. |
I dont think the pull must close the issue; it is clar it can occur for many other fields matteorossi-thespacesm linked a pull request that will close this issue 27 minutes ago |
Indeed I've just made a second pull request to fix another issue on catalog module system.xml |
We are getting this exception on the following core payment methods:
...and many more, also in 3rd party extension. We recoded in Mage/Adminhtml/Model/Config/Data.php to simply not populate these fields with data: We are getting the exception when editing configuration for a store, on website or global level the exception is not throw. It seems that when a config option is disabled for a store view then the "dynamic_group" tag is required to be set. |
See Cannot save any modification for other selection than Default in Configuration Scope #1417 PR that will close this issue: |
fixed by #1418 |
Preconditions (*)
Install SUPEE-11219 – Wrong Field Specified error in 1.9.x
Steps to reproduce (*)
Save settings page wih watermark or any other using dynamic, see stack link
Expected result (*)
Can save config
Actual result (*)
Cannot save config
Code
Issue occurs on line 437 in method public function setGroupsSecure($groups) in file /public_html/app/code/core/Mage/Adminhtml/Model/Config/Data.php
One can remove validation on these specific cases for the dynamic fields
Links hinting to a solution, should be fixed
https://magento.stackexchange.com/questions/302944/supee-11219-wrong-field-specified
or remove the warning ;P
https://www.onooks.com/supee-11219-wrong-field-specified/
The text was updated successfully, but these errors were encountered: