I have just successfully installed Drupal, added multiple pages, blocks, changed themes without any problems. However I cannot figure out how to have multiple stories on a single node. Every time I try to add a new story I can either have it promoted to the front page (which I do not want to do) or have the story go to it's own node. My question is....How do I have multiple stories on a single node, where do I specify this? I do not see an option to specify what node I would like the story to appear on. As a work around I have been using blocks for all my stories which allow me to specify what node each block will appear on.....but I lose a lot of functionality this way......Please help.
c00p
Comments
node vs page
In Drupal a node is the base for most content types such as a story or a page. When you create such content you are typically creating one story (or page, or whatever). A page can be many things but for what you want can be seen as a collection of node based content. The default home page is a listing of all content promoted to the front page. What you want is a collection of stories based on some criteria. So the question for you is what is it that ties stories together. One thing you may want to check out is the book module, it would allow you to group stories together in a book. In this case there would be a page showing all the story titles in a book and by clicking on a title someone could view that story. Each story will have "forward/back" links to other stories in that "book". Another possiblity is to categorize the stories using the taxonomy (or category) module. In this case you might have terms for 'science fiction', 'fantasy', etc and would be able to list all stories in the same category on a page. Of course you relating the stories in some other fashion.
Stories are nodes
You can't put multiple nodes in a node. I think what you are asking is "can I make some sort of listing or combined 'thing' that shows the content of multiple nodes?"
Not quite. When you create a story it will always become a node. Whether or not it shows up on the front page is just an optional extra setting. The default front page is actually the node module showing a listing of node teasers from nodes that have that setting.
I think what you want is to be able to create your own listings. Try looking at the Views module for that, or you could use Taxonomy if you have simpler needs. Or if you feel like coding you could even create another node (using the PHP content type) that includes the content of the nodes you want.
--
Anton
New to Drupal? | Forum posting tips | Troubleshooting FAQ
Example Knowledge Base built using Drupal
look here
Following on from styro's comment, take a look here: http://drupal.org/handbook/customization, for some code snippets that you can insert into a node (eg. page) with the input format set to PHP. In particular, you might find the "PHP and Javascript snippets" section useful.
______________________________________________________________________________________________________
aggravating
See: This is one of the most aggravating aspects of coming to Drupal for the first time. (As I am.) All a new user wants to do is put up a Menu that looks like this:
News:
--Sports
--Politics
...and let's say I want the user to click on 'Sports' and they get the three most recent sports stories. Why can't I find any recent documentation that shows how to do this?
This takes forever to figure out how to do--at least with just using the core modules. Taxonomy? Sure, I get that stories can be categorized. But if you're just using the core, how do you get the taxonomies to correspond to menus? Do we really have to download two other modules to get this basic functionality? Like I said--I'm new and could be missing something, but why is this so convoluted? It's a basic requirement of almost every web site. Can someone just post how to do this?
You do not need any other
You do not need any other modules to do what you explained. If you use taxonomy to categorize your stories you can make a menu where each menu entry has a path like "taxonomy/{tid}" where {tid} is a taxonomy term id. There are also module that can make this easier as they will build menus based on vocabularies.
Sorry, I didn't explain myself correctly....
Thanks for your help. I re-read my last comment and found that I didn't explain myself correctly--The issue isn't getting a menu item to display a term, it's getting it to display a list of entries in a vocabulary. So, while there's no problem displaying 'sports', it seems a little harder to display 'sports' and 'politics' when clicking the 'news' link.
(You're right: Linking terms to menus is very straight forward, and doesn't require anything other than the core.)
There are two ways I know of to solve this issue--I'm including these for other beginners--please let me know if I'm wrong.
1) You can manually create a link that lists two different term ids for the subcategories.
2) You can automate the process using views. (Use views to select a taxonomy vocabulary, then link the menu item to that view.)
By the way, if there is any other way, I'd love to hear it. Thanks.
More than one term
The news link can point to a listing made of nodes tagged with one term OR another, like so:
taxonomy/term/1,2
Or it can point to a listing made of nodes all tagged with terms 1 and 2 (using AND instead of OR here), like so:
taxonomy/term/1+2
And it gets more complex with parent terms and child terms.
Say you have a hierarchical vocabulary. If you *also* want nodes tagged with child terms of term ID 2 to show up in your listing you create an URL link this:
taxonomy/term/1/all
Details: http://drupal.org/handbook/modules/taxonomy
Caroline
11 heavens.com
IMHO you are taking the
IMHO you are taking the wrong approach here. What you are asking about how to do is not "a basic requirement of almost every website". Modules need various types and amounts of overhead i.e. memory, disk space, execution time etc... As such the core ships with what are the basic requirements of almost every website: the ability to store and retrieve content, categorize content, display content in a meaningful and stylized way (themeing) and the ability to create menus (links) to various content on the site.
I think some people find it hard to understand that in fact yes you may have to install an additional module or two (or 3 or 5) so that you get the functionality your particular site needs. The fact that core does not ship with those modules pre-installed or integrated means that when you have a site that does not need some functionality you are not burdened with the overhead of that module.
With the Views module you can easily and quickly achieve what you described and more.