I'm not sure what this means. I was thinking that maybe they would get that having each wine as a separate entry (content type) would eventually give them a nifty database they could do other stuff with. Then I'd make a view that would automatically show the 12 most recent ones. Otherwise I could just make a content type with wine name 1, wine vintage 1, wine name 2, wine vintage 2, etc. but that seems cumbersome.
Are you saying that the 12 wine content nodes could be also input through one form, and then show up as one node, or one view?
Jean
You could create a submit form as a CCK. you can redirect the the path that you want the submit form to show up on from the htaccess file to the node/add/my_cck page. WIll that help? For settings in htaccess, just mail abck and I cna help.ShyamalaTeam Leader<a href=www.netlinkindia.com>Netlink Technologies</a>----- Original Message -----From: William SmithSent: Tuesday, September 11, 2007 5:31 PMSubject: Re: [support] How can I duplicate fields in one content type?The way I understood the problem was that Jean didn't want the end-user/client to have to enter the items individually, but wanted the flexibility of having each item as a distinct node .. so the problem would be more on the input side then on the display side.
I'm not sure if there is an existing contrib module to allow this .. does something exist out there that would let you specify "at <this path> create a submission form for <number> of <node type>" and then create those nodes?
On 9/11/07, Earnie Boyd <earnie@users.sourceforge.net> wrote:Quoting Jean Gazis <jgazis@gmail.com>:
> I don't know any PHP. I have cut and pasted a snippet or two, but that's
> about it. I want to eventually learn more, but this isn't a big-ticket job
> so it's not what I'd choose to put all my time into right now.
>
> Is there a module or modules that would let me do this?
>
If I understand what you need, a simple listing of recently added pages
by page type, yes. Perhaps the archive[1] or calendar[2] is all you
need. The other option is to use a taxonomy term to do grouping. You
create a taxonomy term for each new package. Then you can display the
package using the taxonomy term. From that package you can list the
individual product. You can use a path alias to rename
taxonomy/term/<tid> to something more elegant.
Earnie -- http://for-my-kids.com/
-- http://give-me-an-offer.com/
--
[ Drupal support list | http://lists.drupal.org/ ]
--
[ Drupal support list | http://lists.drupal.org/ ]
--
[ Drupal support list | http://lists.drupal.org/ ]