David - I have been following your exploration of this topic with interest.
We have a similar requirement, but coming at it from the other direction. We need to build a site entirely controlled thru CMS (no ftl files or anything else that requires touching the file system). And then add eCommerce functionality to that site. It would be really great if someone could say whether or not this is even possible before I start down the path of creating all the content. The biggest area I suspect will create limitations to this approach is that there would be no CommonScreens.xml file to perform actions like running bsh scripts. Any insight would be appreciated. Vince Clark Global Era The Freedom of Open Source [EMAIL PROTECTED] (303) 493-6723 ----- Original Message ----- From: "David Goodenough" <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, September 28, 2007 6:03:08 AM (GMT-0700) America/Denver Subject: Re: I am trying to display CMS mananaged content in ecommerce OK, well I managed to get it to work after lots of digging. One thing I am unsure about is the question of associations. For a start at a programming level you are working with an attribute called map-key, finding that this relates to an Association on a Content item is not exactly intuitive. Then I found that it was unclear whether you have to associate the "parent item" (WebStoreContent in this case) with the new item, or the new item with WebStoreContent, or both? If you look in the Association page there are two buttons at the top, Create New and Create New Association, they both seem to do the same thing and there is only one button (Create) at the bottom of the form. Then there are two list, the "Edit Content Association For:...." list and under that the "List Association To:..." list. It is totally unclear what these two lists are, and how you get things onto them - at least when you first start. This brings me to a suggestion. These data entry forms are very bare, they really do not help you to use them. There are no tooltips to provide indications of what the fields do. They are also no indications (until you get an SQL error message in the teeth telling that a required column is not present in the INSERT) as to which fields are required. Also given the amount of white space on the forms, a little bit of explanatory text telling you what this form achieves would make things one whole heap easier for the newcomer. David
