Thanks for your report. What specific aspect of ECO are you using?
I'll have to find time to delve into this more deeply as I've only glanced through the code of the module you are referencing. I think this is more of an issue of the two modules not being compatible because they are modifying the same thing. But I'm happy to see what can be done.
I'm the author of CCK Attribute module. I wrote the module with standard Ubercart hooks to add more attributes for the ordered products, in cart, checkout & billing order, by mimic the UC Attribute module.
First Todd please could you tell me how to reproduce the problem, then let's see what happened with the two modules & solve them out.
Thanks, Todd. So based on how you are using it, I think I'll need to pull it up and look into adding settings further separate out functionality needed vs. what is activated. My goal was to provide options without requiring something to be used that isn't needed.
Trungonly, I haven't been able to spend time on this yet, but my guess is that we both are probably using some of the same hooks to achieve what is needed for each module. This seems logical and I think it points more to limitations with Ubercart itself. I think it was version 2.2 that introduced some very useful new hooks, and perhaps there will be some opportunities to identify some feature requests / code enhancements for Ubercart.
That being said, if this looks the way I'm thinking it will when I spend time on it, there's probably an opportunity for me to modify this module to include a conditional check for CCK Attributes and do some things differently so both can be used. But now I'm probably getting a bit ahead of myself. I'll try to look through this further by the end of the week.
I apologize for the delay. The end of 2010 was extremely hectic and a few things carried over into 2011. Now that I've drastically cut down on projects I'm accepting, I should be able to better schedule some time. I will still be very swamped through at least next Wednesday, but I'll try to get my previous notes pulled up and reviewed by next weekend.
Comments
Comment #1
WebNewCastle commentedHi,
Thanks for your report. What specific aspect of ECO are you using?
I'll have to find time to delve into this more deeply as I've only glanced through the code of the module you are referencing. I think this is more of an issue of the two modules not being compatible because they are modifying the same thing. But I'm happy to see what can be done.
- Matt
Comment #2
trungonly commentedI'm the author of CCK Attribute module. I wrote the module with standard Ubercart hooks to add more attributes for the ordered products, in cart, checkout & billing order, by mimic the UC Attribute module.
First Todd please could you tell me how to reproduce the problem, then let's see what happened with the two modules & solve them out.
Comment #3
todd zebert commented@WebNewCastle thanks for responding.
I'm using it in order to disable the automatic creation of Drupal user accounts on checkout of anon Ubercart users.
If I have enabled "ECO (Extra Customization Options for Ubercart)", regardless of "ECO: Main" and "ECO: Webform" it breaks UC CCK Atrribute.
With the two sub modules disabled, admin/store/settings/eco just displays the commentary about usage and related modules, with no options.
Comment #4
WebNewCastle commentedThanks, Todd. So based on how you are using it, I think I'll need to pull it up and look into adding settings further separate out functionality needed vs. what is activated. My goal was to provide options without requiring something to be used that isn't needed.
Trungonly, I haven't been able to spend time on this yet, but my guess is that we both are probably using some of the same hooks to achieve what is needed for each module. This seems logical and I think it points more to limitations with Ubercart itself. I think it was version 2.2 that introduced some very useful new hooks, and perhaps there will be some opportunities to identify some feature requests / code enhancements for Ubercart.
That being said, if this looks the way I'm thinking it will when I spend time on it, there's probably an opportunity for me to modify this module to include a conditional check for CCK Attributes and do some things differently so both can be used. But now I'm probably getting a bit ahead of myself. I'll try to look through this further by the end of the week.
Comment #5
todd zebert commentedWebNewCastle thanks.
BTW, and this may be my inexperience with modules in general, so I tried changing the weight of both these modules, but it didn't make a difference.
Comment #6
WebNewCastle commentedHmm. I'm not sure. It does seem like changing weights would have had some effect - I have done a lot with that so I'm not extremely familiar with it.
But I'm pulling up the code of both modules right now to make some initial notes.
Comment #7
WebNewCastle commentedOk. I identified something to try, and I'll try to find time to work on it over the next few days.
Comment #8
todd zebert commented@WebNewCastle Just checking on the status of any resolution. I know it's a busy time of year. Thanks!
Comment #9
summit commentedSubscribing, greetings, Martijn
Comment #10
WebNewCastle commentedHi,
I apologize for the delay. The end of 2010 was extremely hectic and a few things carried over into 2011. Now that I've drastically cut down on projects I'm accepting, I should be able to better schedule some time. I will still be very swamped through at least next Wednesday, but I'll try to get my previous notes pulled up and reviewed by next weekend.
Thanks for your patience,
Matt
Comment #11
todd zebert commentedThanks Matt! I'm hoping to use ECO and UC CCK in production together by the end of Feb.