Thanks again Michael.
In our model the price is only valid for a certain range of dates, which is why we needed a M:1 for Prices:Products, which is also why I suggested having a separate price object.  Can you use the PLP to add multiple price objects underneath the product?
 
MJS:  That is the way adding images and files work.  For every page you can add a multitude of images and files.  This is how we are going about doing options as well.  Take a look at the step in the dmHTML type for files and images.  You will see the process essentially allows you to add as much as you want to one type.  If I had some finished code I would send it your way, but right now it is pretty messy.  
 
Ahh... so you can embed PLPs inside PLPs pretty much (I should have realised that because you could not only Add images but Create new images when creating a new HTML object). Ok, FarCry is better than I first realised... (this is were Geoff chimes in telling us about his upcoming Breeze presentation :)
  I'm trying to keep out of the core and see how flexible this is.... although with custom sales reports, marketing reports and all the rest I think that's going to be quite hard. I'd prefer to utilise the FarCry and FourQ libraries in a separate app to create some of the custom features, so we can keep with the standard farcry_core. Do you think it's worth the bother?
 
MJS: Our approach for ecom is that there is so much to do to that is intrinsic to the app that we went right to the core.  Custom types are powerful and in some cases we have moved custom types into the core.  We are not messing with the core files in anyway but rather deploying new types in the core.  This will allow us to keep up to date on core builds but have a slew of types for ecom only!
I am going to try custom tabs for vouchers, specials and orders... don't know about custom reporting though. Reports and monitoring is the most important part of e-comm. Maybe I should just do another custom admin tab for our reporting...

Cheers,
Tim


Michael @Four Eyes spoke the following wise words on 21/10/2003 3:11 AM EST:
Thanks for the advice Michael.
 
MJS: This is a community and we all like to help where we can. :)

In our model the price is only valid for a certain range of dates, which is why we needed a M:1 for Prices:Products, which is also why I suggested having a separate price object.  Can you use the PLP to add multiple price objects underneath the product?
 
MJS:  That is the way adding images and files work.  For every page you can add a multitude of images and files.  This is how we are going about doing options as well.  Take a look at the step in the dmHTML type for files and images.  You will see the process essentially allows you to add as much as you want to one type.  If I had some finished code I would send it your way, but right now it is pretty messy.  
 
  I'm trying to keep out of the core and see how flexible this is.... although with custom sales reports, marketing reports and all the rest I think that's going to be quite hard. I'd prefer to utilise the FarCry and FourQ libraries in a separate app to create some of the custom features, so we can keep with the standard farcry_core. Do you think it's worth the bother?
 
MJS: Our approach for ecom is that there is so much to do to that is intrinsic to the app that we went right to the core.  Custom types are powerful and in some cases we have moved custom types into the core.  We are not messing with the core files in anyway but rather deploying new types in the core.  This will allow us to keep up to date on core builds but have a slew of types for ecom only!
---
You are currently subscribed to farcry-dev as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]

Reply via email to