This issue seemed to start after we migrated the data over from Magento 1 so not sure if that had something to do with it.
Is there a way to fix this and get the rules working as they should again?
I currently have a problem with Magento 2 (2.2.7) where I cannot select conditions in the Catalog or Cart price rules. This problem also occurred on Magento 1 and seems to have migrated across along with the sales rules.
The process I undertake is as follows:
Magento Admin 404 Error Page not found.
With the developer console open the following errors appear:
VM24673 legacy-build.min.js:1 POST https://www.websitename.com/admin_panel/sales_rule/promo_quote/newConditionHtml/form/sales_rule_formrule_conditions_fieldset_/form_namespace/sales_rule_form/key/bb452ffee837d48c5d6571c63127dea9581b51d4544b844c3e2592f83013b06d/?isAjax=true 403 (Forbidden) request @ VM24673 legacy-build.min.js:1 initialize @ VM24673 legacy-build.min.js:8 (anonymous) @ VM24673 legacy-build.min.js:1 g @ VM24673 legacy-build.min.js:1 addRuleNewChild @ VM25381 rules.js:318 hideParamInputField @ VM25381 rules.js:281 M @ VM24673 legacy-build.min.js:8 ListPicker._handleMouseUp
VM25381 rules.js:352 GET https://www.websitename.com/admin_panel/sales_rule/index/index/key/26a494ef284767a4336e676435089056fe4f35b809bd43a76062c9b7f707b331/ 404 (Not Found) _processFailure @ VM25381 rules.js:352 respondToReadyState @ VM24673 legacy-build.min.js:8 onStateChange @ VM24673 legacy-build.min.js:1 XMLHttpRequest.send (async) request @ VM24673 legacy-build.min.js:1 initialize @ VM24673 legacy-build.min.js:8 (anonymous) @ VM24673 legacy-build.min.js:1 g @ VM24673 legacy-build.min.js:1 addRuleNewChild @ VM25381 rules.js:318 hideParamInputField @ VM25381 rules.js:281 M @ VM24673 legacy-build.min.js:8 ListPicker._handleMouseUp
I've looked through the log files including system.log and there don't seem to be any messages relating to the cart/catalog rules the Apache log has given me the following error.
GET /website-admin/sales_rule/index/index/key/ed104bf5def6f334de21dd5adc5ccb32e1228ef68b0639363ed5e2a369ec2ab3/ HTTP/1.0
This issue seemed to start after we migrated the data over from Magento 1 so not sure if that had something to do with it.
Is there a way to fix this and get the rules working as they should again?
Hi - did you manage to resolve this? Getting the same error on 2.2.6.
Best regards