FYI, as of December 8, 2014, I just tried to use the dev 2.x branch of commerce product options, and of course I had issues. Yes if someone is using dev for dependent modules... user beware.

I carefully removed dependent fields and modules. Put in the 7.x-1.0-beta2 of commerce_option, reinstalled and yes I am getting past issues.

IF you could mention in the dependencies to avoid the 2.x branch of commerce_option it might help newbies. Either way you can mark this issue as closed after reading.

Thanks for this module.

Comments

webengr’s picture

Issue summary: View changes
fugazi’s picture

I confirm, I do not even happened, and unfortunately you have to do a lot of work then the problem again dishonored in any way. An information would be very important. It would also be very nice if 2.x is compatible with 7.x-1.0-Beta 4. That would be a perfect meeting. !!!

trumanru’s picture

Priority: Minor » Normal
deminy’s picture

+1

I ran into same issue as what @webengr experienced. I'd highly suggest to update documentation clearly telling user which version/branch of module Commerce Product Options to be used. Thanks

FranCarstens’s picture

+1 This is definitely something that should be clearly stated in documentation.

bisonbleu’s picture

As a simple first step, I suggest changing the first paragraph of the project page to something like this:

Commerce pricing attributes (cpa) provides some enhancements to the Commerce Product Option (7.x-1.x branch) and Commerce Product Attributes handling by applying pricing rules to custom product attributes.

p.s.1. cpa is extremely useful. It works well with commerce_option-7.x-1.x. Let's work together to make it better.
p.s.2. If I could edit the project page, I would.

gbyte’s picture

I created a small sandbox module to temporary replace this module for the 2.x branch of commerce product options. Feel free to check it out here. The sandbox is a simplified version of this module and might not fit every use case.

FranCarstens’s picture

This thread is almost 2 years old and the project page still does not indicate that this module is ONLY compatible with commerce_option-7.x-1.x.

Can we be honest and have the project page updated to:

  • Maintenance status: Unsupported
  • Development status: No further development
nchar’s picture

I changed the module's statuses. Also noted with strong text that it only works with commerce_option-7.x-1.x. If anyone is interested in becoming maintainer and fixing the issues please reply here.

whop’s picture

for me it works with branch 2
hmm