I want to have a content type for a monthly list of about a dozen wine selections. I created the content type, and created fields for one wine, and I can add new fields or existing fields from a _different_ content type, but I don't see any way to copy the first set of fields on the _same_ content type. Is there a reason for this? Do I have to have Name for wine #1, and then Name2 for wine #2 and so on?
Would I be better off to have a content type for "wine" and then have a view that shows the 12 most recent?
Yes, it's better for you to have a content type for "wine", and then you can do different things with it. Think of a wine as one entity. 12 wines can be an entity if they are bundled in one package, but a single wine should be on its own.
Jean Gazis wrote:
I want to have a content type for a monthly list of about a dozen wine selections. I created the content type, and created fields for one wine, and I can add new fields or existing fields from a _different_ content type, but I don't see any way to copy the first set of fields on the _same_ content type. Is there a reason for this? Do I have to have Name for wine #1, and then Name2 for wine #2 and so on?
Would I be better off to have a content type for "wine" and then have a view that shows the 12 most recent?
-- Jean Gazis www.jeangazis.com http://www.jeangazis.com www.boxofrain.us http://www.boxofrain.us
"Believe those who are seeking the truth; doubt those who find it." - André Gide
I think that probably provides more flexibility in the long run. It's not an e-commerce site. I'm concerned the the client will find entering 12 items separately more cumbersome than just doing one form.
Jean
On 9/10/07, Zohar Stolar z.stolar@gmail.com wrote:
Yes, it's better for you to have a content type for "wine", and then you can do different things with it. Think of a wine as one entity. 12 wines can be an entity if they are bundled in one package, but a single wine should be on its own.
Jean Gazis wrote:
I want to have a content type for a monthly list of about a dozen wine selections. I created the content type, and created fields for one wine, and I can add new fields or existing fields from a _different_ content type, but I don't see any way to copy the first set of fields on the _same_ content type. Is there a reason for this? Do I have to have Name for wine #1, and then Name2 for wine #2 and so on?
Would I be better off to have a content type for "wine" and then have a view that shows the 12 most recent?
-- Jean Gazis www.jeangazis.com http://www.jeangazis.com www.boxofrain.us http://www.boxofrain.us
"Believe those who are seeking the truth; doubt those who find it." - André Gide
-- [ Drupal support list | http://lists.drupal.org/ ]
You could always get the best of both worlds by doing what Zohar suggests re: making each item an individual node, but also providing a single form interfacing for submitting a collection. In this case, on form submission, the individual nodes would be programatically created in the backend. You could even do the magic of creating the 'collection' view at this stage. It could either be dead-simple or prohibitively difficult to set this up, depending on your level of familiarity with PHP and the Forms API.
William
On 9/10/07, Jean Gazis jgazis@gmail.com wrote:
I think that probably provides more flexibility in the long run. It's not an e-commerce site. I'm concerned the the client will find entering 12 items separately more cumbersome than just doing one form.
Jean
On 9/10/07, Zohar Stolar z.stolar@gmail.com wrote:
Yes, it's better for you to have a content type for "wine", and then you can do different things with it. Think of a wine as one entity. 12 wines can be an entity if they are bundled in one package, but a single wine should be on its own.
Jean Gazis wrote:
I want to have a content type for a monthly list of about a dozen wine selections. I created the content type, and created fields for one wine, and I can add new fields or existing fields from a _different_ content type, but I don't see any way to copy the first set of fields on the _same_ content type. Is there a reason for this? Do I have to have Name for wine #1, and then Name2 for wine #2 and so on?
Would I be better off to have a content type for "wine" and then have a view that shows the 12 most recent?
-- Jean Gazis www.jeangazis.com http://www.jeangazis.com www.boxofrain.us <http://www.boxofrain.us >
"Believe those who are seeking the truth; doubt those who find it." - André Gide
-- [ Drupal support list | http://lists.drupal.org/ ]
-- Jean Gazis www.jeangazis.com www.boxofrain.us
"Believe those who are seeking the truth; doubt those who find it." - André Gide
-- [ Drupal support list | http://lists.drupal.org/ ]
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?
Jean
On 9/10/07, William Smith william.darren@gmail.com wrote:
You could always get the best of both worlds by doing what Zohar suggests re: making each item an individual node, but also providing a single form interfacing for submitting a collection. In this case, on form submission, the individual nodes would be programatically created in the backend. You could even do the magic of creating the 'collection' view at this stage. It could either be dead-simple or prohibitively difficult to set this up, depending on your level of familiarity with PHP and the Forms API.
William
On 9/10/07, Jean Gazis jgazis@gmail.com wrote:
I think that probably provides more flexibility in the long run. It's not an e-commerce site. I'm concerned the the client will find entering 12 items separately more cumbersome than just doing one form.
Jean
On 9/10/07, Zohar Stolar < z.stolar@gmail.com> wrote:
Yes, it's better for you to have a content type for "wine", and then you can do different things with it. Think of a wine as one entity. 12 wines can be an entity if they are bundled in one package, but a single wine should be on its own.
Jean Gazis wrote:
I want to have a content type for a monthly list of about a dozen
wine
selections. I created the content type, and created fields for one wine, and I can add new fields or existing fields from a _different_
content type, but I don't see any way to copy the first set of
fields
on the _same_ content type. Is there a reason for this? Do I have to have Name for wine #1, and then Name2 for wine #2 and so on?
Would I be better off to have a content type for "wine" and then
have
a view that shows the 12 most recent?
-- Jean Gazis www.jeangazis.com http://www.jeangazis.com www.boxofrain.us <http://www.boxofrain.us >
"Believe those who are seeking the truth; doubt those who find it."
André Gide
-- [ Drupal support list | http://lists.drupal.org/ ]
-- Jean Gazis www.jeangazis.com www.boxofrain.us
"Believe those who are seeking the truth; doubt those who find it." - André Gide
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
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/
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/ ]
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.
Shyamala Team Leader <a href=www.netlinkindia.com>Netlink Technologies</a> ----- Original Message ----- From: William Smith To: support@drupal.org Sent: Tuesday, September 11, 2007 5:31 PM Subject: 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/ ]
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
On 9/11/07, Rajaram Shyamala shyamala@netlinkindia.com wrote:
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.
Shyamala Team Leader <a href=www.netlinkindia.com>Netlink Technologies</a>
----- Original Message ----- *From:* William Smith william.darren@gmail.com *To:* support@drupal.org *Sent:* Tuesday, September 11, 2007 5:31 PM *Subject:* 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/ ]
-
Earnie Boyd -
Jean Gazis -
Rajaram Shyamala -
William Smith -
Zohar Stolar