By vikramdhani on
hi i am in a process to have a mobile phones blog and i want to make pages linked to the specific menu links and i know i have to use the taxonomy for that but the hanbook for this is very confusing and i m not been able to understand anything so i am here trying to see if anyone can help me understand this taxonomy work better
what i am tryin to do is something like this
menu links:
iphone
windows mobile
symbiam
now i want the taxonomy to work in way when i will submit stories i should be able to attach the new created page with a categories so that when a user will click on iphone link will be able to see all the pages posted for iphone
Need some help please
Comments
Enable Taxonomy module, then
Enable Taxonomy module, then at admin/content/taxonomy create a vocabulary for your categories and enable it for the content type of your stories. Now add the terms (iphone, windows mobile, symbiam) to your new vocabulary.
Now, go to "create content" (node/add) and create a story. In the node input form you should see a select list that allows you to associate your new post with one of your new categories/terms. Create a story for each term. On the respective story's node output page you should see a link that's called like your category. That link leads to a page that lists all stories that are associated with that term.
Copy the path to that page and go to "Administer -> Site building -> Menus" (admin/build/menu) and create a new menu item in the menu in which you would like your menu links to appear. There you can link to the path of the taxonomy term page and choose a link title for the menu item. After saving the new menu item it will be part of the menu and link to the taxonomy term page of your category. This you can do for each of your categories (iphone, windows mobile, symbiam).
good
That's a pretty concise explanation. Good one!
Note, the 'taxonomy term page' will look something like 'taxonomy/term/2' - you can find out the number by looking at the edit page for that taxonomy term.
If you use pathauto, things will change, but the answer will be in the same place.
Unfortunately new menu items still don't magically appear without help from taxonomy_menu.module (which I do not recommend) so you are best to just remember to add the third step- creating menu items by hand - any time you add something to the taxonomy.
.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/
.dan. is the New Zealand Drupal Developer working on Government Web Standards
taxonomy_menu
Hello Dan,
I just read your comment to the taxonomy question, and I´m wondering why you don´t recommend the taxonomy_menu? I just decided to use it, but was not sure about it either...
And I have got another question... maybe you can have a look at it..
http://drupal.org/node/225804
It is a taxonomy question as well...
Thanks a lot.
taxonomy_menu uses a custom
taxonomy_menu uses a custom format for its URL paths which doesn't match up with the built in (or views) version of the same thing.
So if you nav through taxonomy_menu to be at location /2/3/35/66 it's not the same place as taxonomy/term/66. Although it displays the same info. Sorta.
And if you DO visit taxonomy/term/66, like by clicking on the tag link for a node, the appropriate taxonomy_menu you'd want to see doesn't appear.
And then things get even hairier if you try to enable pathauto or even aliases.
There may be work-arounds, I'm sure folk have been looking for them, but I haven't found a way to keep most of Drupal link conventions working with add-on modules, AND have taxonomy_menu be anything but confusing.
It's a shame, because it would be a killer and obvious util otherwise. It's OK if that's ALL you want and don't read URL paths, but it breaks too many Drupal conventions for me to work happily with it.
I even wrote my own version which behaves like taxonomy_menu but keeps Drupal term paths. Unfortunately it involves rewriting the menu table every time anything gets updated. So far. And recently got misconfigured and went recursive polluting my menu table with a hundred copies of itself :-) so it's not really ready to replace the other module any time soon.
.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/
.dan. is the New Zealand Drupal Developer working on Government Web Standards
thanks for the help
thanks for the help