And how was this done... I can't get it done with the category module...

gdev - October 20, 2006 - 12:39

This category info site http://category.greenash.net.au/docs has exactly the structure I need for my site...

This is what I do :

1) I make a container and want it to go into a custom menu... but even if I select that the link should be in the custom menu, it appears in the navigation menu, and I have to move it manually to the custom menu.

2) I make categories for the subjects. So and want the content nodes to be listed under the description. But it just can't get it to work in a way that it looks like in that site!

Gdev

Book module

geodaniel - October 20, 2006 - 13:49

Not entirely sure I understand your question... but that page has been created with the book module to create the structure of the pages. Sounds like you may have been trying to use the taxonomy module instead?

Not the book module

Michelle - October 20, 2006 - 14:44

That site was created with the Category module... That's the whole point of it.

Sorry, can't help with the original quesiton. I'm still trying to understand Category myself.

Michelle

--------------------------------------
My site: http://shellmultimedia.com

I should have read the text

geodaniel - October 20, 2006 - 14:58

I should have read the text of the site I guess :) I just looked at the structure of the page and glanced over the text, d'oh. Likewise, I can't really answer anything about category module, sorry.

Since Jaza let me take a

venkat-rk - October 20, 2006 - 15:47

Since Jaza let me take a peek at the structure, here is how he did it:

1.) Docs is a container, with some description added
2.) Features is a child container of Docs and all the stuff beneath it (category display features, category export features are just category nodes- meaning, you add a category, enter text in the body area and you are done
3.) Installation and Tutorials are similarly child containers of Docs with descriptive text in the body area and category nodes of their own as their children
4.) Category vs taxonomy and book, Multiple root categories, Using activeselect with category, Using pathauto with category, Using views with category, Using taxonomy-dependent modules, Why all of this isn't on drupal.org are all categories of the Docs container used as nodes.

Just remember to set the prev/up/next navigation for all the containers you create (Docs, Features, Installation and Tutorials) so that you can go through the entire category tree for the Docs section from beginning to end by clicking on the navigation links.

He has also styled the site to use a single-column page. That's about it.

trying to use category community

volunteermama - October 20, 2006 - 17:30

It would be nice to have a trying to understand category community!
These posts seem similar...
http://drupal.org/node/89484
http://drupal.org/node/77002#comment-164964
http://drupal.org/node/89626#comment-164974
this one is old but seems to be asking similar questions:
http://drupal.org/node/75197
http://drupal.org/node/86265

Can anyone point to another thread or location of similar discussions that go a bit further?

prev/up/next navigation on tagged nodes

AdAstra - December 13, 2006 - 00:59

We can browse through the entire Docs container using prev/next because information is displayed on child containers or categories.

How about displaying prev/next links on nodes tagged to a category? I created a 'story', tagged it with category1, all menus and breadcrumbs are in place. But the prev/nav links do not appear.

Was the category module designed this way, or is there a bug?

-------------------------------------------------
AdAstra.ca - Optimze the Web. Optimze the World.

Was the category module

venkat-rk - December 13, 2006 - 06:02

Was the category module designed this way, or is there a bug?

I am not a category expert, but I think it was designed that way. The ToC and prev/up/next links are for the containers and their child categories, There's only the regular drupal pager display for the assigned nodes.

I think part of the logic behind this may have been that containers and categories are both drupal node types, so you can use them in lieu of other node types and still tag those same categories too!, which would give the prev/up/next links for those nodes.

But, yes, this would be a handy feature for the other node types.

----
Previously user Ramdak.

Have your category and eat it too

AdAstra - December 14, 2006 - 01:04

We can always count on Ramdak for a prompt response :)

I see what you mean. I can create a story node, tag it with a category (like tagging with taxonomy), and enable the "story type to behave like category" option, so that the node benefits from TOC, prev/up/next links, etc.

Cool, thanks!

-------------------------------------------------
AdAstra.ca - Optimze the Web. Optimze the World.

Great:-) Actually, you took

venkat-rk - December 14, 2006 - 06:01

Great:-)

Actually, you took it a step further by using category_transform (story node into category), whereas I only meant using containers and categories as nodes. Different ways of doing pretty similar things. Shows how flexible the module is.

----
Previously user Ramdak.

 
 

Drupal is a registered trademark of Dries Buytaert.