I publish a webcomic. On my site I make rather heavy use of taxonomy, to allow my readers to filter my comic archives in a few interesting ways. One of these taxonomy terms is "storyline" and it essentially groups together every comic that belongs to the same story arc.
Every comic node contains a storyline link which allows the reader to view all of the comics in that story arc together, 5 to a node. For example, the very first storyline for my comic Help Desk is called "The Beginning," and the taxonomy link for that storyline is http://ubersoft.net/comic/hd/storyline/beginning. If you click on that link you'll see four comics. The earliest published comic in that story arc is at the top of the page, the latest published comic in that story arc is at the bottom of the page. So it looks like this:
1
2
3
4
That is how it works in DRUPAL 5. I am currently upgrading the site to DRUPAL 6, and I've noticed that the taxonomy node now reverses the order the comics appear in, so that they now display in this order:
4
3
2
1
Obviously that doesn't work well in this situation -- I want the reader to be able to view the story arc sequentially, and Drupal is displaying it "blog style" which is exactly the opposite of what I want -- and what it did in D5.
So I have two questions:
1. Is there a way to make Drupal6 show these comics in the order I want them to?
2. If not, is there a way to create a view that essentially overwrites those nodes so I can sort the comics the way I want? I have been able to create a view that does this but I haven't been able, so far, to have that view actually replace the default node.
Thanks in advance for any suggestions you might have.
Comments
Drupal has always done it in
Drupal has always done it in reverse date order. Not sure what you had happening before, but 4-3-2-1 is normal.
You have the solution - yes you just make a view, and set it to the sort order you want.
BUT there may be a hidden step to get the url-aliases you want.
If your 'beginning' term is term id 17, then the Drupal URL is taxonomy/term/17, and you can make an URL Alias
.../storyline/beginning -> taxonomy/term/17
I do not know, but imagine this can be set up with pathauto, but it's probably OK to do a dozen by hand.
.dan.
if you are asking a question you think should be documented, please provide a link to the handbook where you think the answer should be found.
| http://www.coders.co.nz/ |
.dan. is the New Zealand Drupal Developer working on Government Web Standards
Alas, it doesn't work...
... I already use pathauto, and it already creates the aliases automatically. The problem is that when I make a view with the same URL (it's not too hard to do that if you use arguments) the view won't take the place of the node. In other words: if the node and the view have the same URL, when I use that URL I see the node, not the view.
I had thought that views were supposed to supercede nodes automatically, but apparently not in this case...
Also, it won't be practical to do this by hand. I've been publishing this comic for almost 13 years and I have hundreds of storyline taxonomy terms...
your index pages are nodes?
A list of items - such as that provided by taxonomy/term/n - is not a node.
If you manually create individual nodes with an URL that over-rides a specific view - it will indeed override because it's more specific than the wildcard match.
But it will - as well as that drawback - cause maintenance headaches.
Why do you have actual nodes in place of views or term listings?
I thought that was a small typo before - but are you saying you have created static nodes that represent the lists - instead of using the available list-building tools?
Stop using nodes for index pages. Or use node-as-tem nat.module to do both.
.dan.
if you are asking a question you think should be documented, please provide a link to the handbook where you think the answer should be found.
| http://www.coders.co.nz/ |
.dan. is the New Zealand Drupal Developer working on Government Web Standards
I may be misusing the terminology...
... Drupal's terminology is still a bit difficult for me to grasp, even after using it for two years.
Let me explain what I have and you can tell me what it's called. :)
I created a taxonomy category called "Storyline." On each comic I upload to Drupal I fill out a free-form text field called "Storyline" that associates the comic to a specific term in that category. If multiple comics use the same label, they are all grouped under the same term. In this way I can separate comics by story arcs, and when viewing an individual comic it is possible for the reader to click on the storyline name in order to view all the comics tagged with that term.
Here is an example of this:
http://ubersoft.net/comic/hd/storyline/lawsuit-grinding
The storyline "Lawsuit Grinding" has three comics associated with it:
http://ubersoft.net/comic/hd/2008/12/there-ever-convenient-time
http://ubersoft.net/comic/hd/2009/01/pulling-mob
http://ubersoft.net/comic/hd/2009/01/boss-monster
When you click on the storyline link on any of these comics it takes you to the link above, which displays all three comics, with the earliest published comic on the top of the page, then the next, then the next.
It's not a view or a page so I called it a "node." That's all.
I still can't get it to work the same way in D6 that it does in D5, though.
http://ubersoft.net/taxonomy/
http://ubersoft.net/taxonomy/term/382
That is effectively a view - in D5 maybe not a views.module view, but that's the functionality (from taxonomy) that views extended.
Nodes are one lump of content. That's a collection of content.
So all you've been trying to do should work, it's probably something simple missing in your process.
Make a view - Using the term over-ride feature it gives you. Then override the sort order. Sort out your pathauto as needed.
.dan.
if you are asking a question you think should be documented, please provide a link to the handbook where you think the answer should be found.
| http://www.coders.co.nz/ |
.dan. is the New Zealand Drupal Developer working on Government Web Standards