As far as I've been able to tell (mostly from the deafening silence), Products.CompoundField is unmaintained. It's not terribly interesting anymore, because z3c provides listish capabilities anyway. But that's not all that helpful if you're already invested in CompoundField, as we are. It doesn't work with Plone 4, last I checked, and if you're committed to Archetypes for this project, then I would say your best bet is to use related items or a preset catalog search to meet your needs (as you described).
Anyway, glad someone's making use of my patch. :) Best wishes, Michael A. Smith Web & Digital / Academic Technologies Manager Nazareth College ----- "Kees Hink" <[email protected]> wrote: > I'm currently trying to to use CompoundField to create a field for an > array of > images, but i'm getting bitten by > http://plone.org/products/compoundfield/issues/12: CompoundField > returns a > string as its accessor. > > This could be fixed by a minor tweak in a Products.Archetypes page > template > (patch supplied in issue above). I'd be happy to check that Archetypes > and > CompoundField work well together in this respect, a new release could > be made > and all would be well. The question is, do we want to do this with > Archetypes > just to make Products.CompoundField work? > * No, CompoundField seems to be abandoned, don't bother. > * Yes, it would solve a common use case. > > Or are there other options, a successor to CompoundField? It would > have to be > Archetypes-based, because the production site i'm working on is > Archetypes-based. For now, i have a deadline and will set a reference > to a > folder where the images are stored. > > Kees > _______________________________________________ > Product-Developers mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/product-developers _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
