Mage::dispatchEvent('salesrule_rule_condition_combine', array('additional' => $additional));<\/code><\/pre>\n\n\n\nwill trigger an observer than will actually do the work of combining the dropdown options. This is TRYING to call an observer defined in:<\/p>\n\n\n\n
app\/code\/local\/Amasty\/Shiprestriction\/etc\/config.xml<\/pre>\n\n\n\n<salesrule_rule_condition_combine>\n <observers>\n <amasty_shiprestriction_model_observer>\n <type>singleton<\/type>\n <class>amshiprestriction\/observer<\/class>\n <method>handleNewConditions<\/method>\n <\/amasty_shiprestriction_model_observer>\n <\/observers>\n<\/salesrule_rule_condition_combine><\/code><\/pre>\n\n\n\nAnd this is where we finally get to the flaw. The observer, salesrule_rule_condition_combine<\/strong>, is already defined by the Enterprise Customer Segment module.<\/p>\n\n\n\napp\/code\/core\/Enterprise\/CustomerSegment\/etc\/config.xml<\/pre>\n\n\n\nBecause there are two observers with the same name, only one can get used and the Enterprise module wins. So because the configuration is set to add Customer Segments the Shipping Restrictions module doesn’t correctly combine it’s options into the dropdown. However, if you had the Customer Segments option set to no, then the Customer Attributes would show in the dropdown.<\/p>\n\n\n\n
The Fix for the Bug<\/h2>\n\n\n\n
The solution to this bug is simple really – the name of the observer for the Amasty Shipping Restrictions extension needs to be changed to not conflict with the Enterprise module.<\/p>\n\n\n\n
This solution will call two observers – one for the Amasty Shipping Restrictions module to add the Customer Attributes<\/strong> submenu and then to the Enterprise Customer Segment module which will add the Customer Segments<\/strong> options.<\/p>\n\n\n\nChange the Observer Name<\/h3>\n\n\n\n
File:<\/p>\n\n\n\n
app\/code\/local\/Amasty\/Shiprestriction\/etc\/config.xml<\/pre>\n\n\n\nChange This:<\/p>\n\n\n\n
<salesrule_rule_condition_combine>\n ...\n<\/salesrule_rule_condition_combine><\/code><\/pre>\n\n\n\nTo This:<\/p>\n\n\n\n
<amshiprestriction_salesrule_rule_condition_combine>\n ...\n<\/amshiprestriction_salesrule_rule_condition_combine><\/code><\/pre>\n\n\n\nCall the New Observer Name<\/h3>\n\n\n\n
File:<\/p>\n\n\n\n
app\/code\/local\/Amasty\/Shippingrestrictions\/Model\/Condition\/Combine.php<\/pre>\n\n\n\nAdd this line on line 33:<\/p>\n\n\n\n
Mage::dispatchEvent('amshiprestriction_salesrule_rule_condition_combine', array('additional' => $additional));<\/code><\/pre>\n\n\n\nFor clarity sake, this should be added after this line:<\/p>\n\n\n\n
Mage::dispatchEvent('salesrule_rule_condition_combine', array('additional' => $additional));<\/code><\/pre>\n\n\n\nClear the Cache<\/h3>\n\n\n\n
Because we made a modification to the XML you’ll need to choose System -> Cache Managmeent and clear the following caches:<\/p>\n\n\n\n
- Configuration<\/li>
- Layotus<\/li>
- Blocks HTML Output<\/li><\/ul>\n\n\n\n
Now, refresh the Amasty Shipping Restrictions rules page and you’ll see all of the desired options in the dropdown.<\/p>","protected":false},"excerpt":{"rendered":"
I came across this issue, which admittedly may have a small affect for Magento installations, but it’s something […]<\/p>\n","protected":false},"author":1,"featured_media":1367,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wprm-recipe-roundup-name":"","wprm-recipe-roundup-description":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[46,5],"tags":[],"class_list":["post-1357","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-magento","category-website-development"],"jetpack_featured_media_url":"https:\/\/promincproductions.com\/blog\/wp-content\/uploads\/2016\/05\/Magento-EE-Amasty-Shipping-Restrictions-Bug.jpg","jetpack_shortlink":"https:\/\/wp.me\/p4BbcR-lT","jetpack_sharing_enabled":true,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/promincproductions.com\/blog\/wp-json\/wp\/v2\/posts\/1357","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/promincproductions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/promincproductions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/promincproductions.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/promincproductions.com\/blog\/wp-json\/wp\/v2\/comments?post=1357"}],"version-history":[{"count":13,"href":"https:\/\/promincproductions.com\/blog\/wp-json\/wp\/v2\/posts\/1357\/revisions"}],"predecessor-version":[{"id":2030,"href":"https:\/\/promincproductions.com\/blog\/wp-json\/wp\/v2\/posts\/1357\/revisions\/2030"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/promincproductions.com\/blog\/wp-json\/wp\/v2\/media\/1367"}],"wp:attachment":[{"href":"https:\/\/promincproductions.com\/blog\/wp-json\/wp\/v2\/media?parent=1357"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/promincproductions.com\/blog\/wp-json\/wp\/v2\/categories?post=1357"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/promincproductions.com\/blog\/wp-json\/wp\/v2\/tags?post=1357"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Conflicts](\"https:\/\/promincproductions.com\/blog\/wp-content\/uploads\/2016\/05\/Magento-EE-Amasty-Shipping-Restrictions-Bug.jpg\")
<\/a>