Closed (fixed)
Project:
Commerce Core
Version:
7.x-1.x-dev
Component:
Product pricing
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Mar 2014 at 00:00 UTC
Updated:
26 Apr 2014 at 01:10 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
stevesmename commentedComment #2
stevesmename commentedComment #3
rszrama commentedNot really a bug. Let's just make sure it's all kosher and that the UI module has the requisite dependencies in place.
Comment #4
rszrama commentedWait, maybe I'm not understanding how you've phrased the original post, but it doesn't read correctly to me. Why would Commerce Product Pricing be considered's a developer module? Are you sure it's not being disabled because it depends on Rules UI, not vice versa?
Comment #5
stevesmename commentedGuess I was speaking on behalf of the customer. The customer had a custom module that extended functionality from Commerce Product Pricing. The customer is hosted on a Drupal hosting company and the hosting company highly suggests to turn off UI modules by Disabling Developer Modules. With the admin_menu module you get the ability to Disable Developer Modules, when developer clicks this functionality then Commerce Product Pricing is disabled because it depends on Rules UI and that in turns disable any custom modules.
Comment #6
bojanz commentedThat admin_menu option is a dumb idea that constantly results in wrong modules getting disabled. I've seen it all over Commerce contrib, and wider.
Comment #7
andyg5000This bug is melting commerce sites around the globe!
Rules admin should only be a dependency of the commerce_product_pricing_ui module. Patch is good to go :D
Comment #8
rszrama commentedPssh, it's melting Commerce sites that use an ill advised "feature" in Admin Menu that is. ; )
Committed.