Display multiple breadcrumbs
joel_guesclin - September 7, 2007 - 13:21
| Project: | Taxonomy context |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Description
I've always wanted to be able to display multiple breadcrumbs (like Amazon does) - so the vocabulary listing at the bottom of a node looked really good to me. But there were a few problems:
- it appeared at the bottom, and most of my nodes are really long so I wanted it at the top
- it doesn't display breadcrumbs but a list, which I didn't like as much
- and you couldn't exclude vocabularies from the list (for example, I don't want people seeing my "site structure" vocabulary there)
- the list of terms appeared in the teaser where it isn't wanted, instead of just in the node
So I have produced a patch which takes care of all that and here it is: you can switch on/off the "Full breadcrumbs" feature per content type, the full breadcrumbs appear at the top of the node in a collapsible fieldset, and you can exclude vocabularies in the general settings. Comments would be welcome of course.
| Attachment | Size |
|---|---|
| taxonomy_context_3.patch | 4.2 KB |
#1
Sounds great to me, but I can't get your patch to apply cleanly. It complains about "misordered hunks".
You really should be making unified diffs instead of "normal" diffs, especially since there are no releases for this project so I have no way of knowing which version of the code you started with.
#2
I'm using 5.x-1.x-dev (the only version available for download) - I'm afraid I've no idea what is the difference between a unified and a normal diff
#3
5.x-1.x-dev isn't a static release- it's more like a snapshot, which could get updated at any time.
A normal diff (the default for the diff command) just gives the changes and line numbers. But if we happen be using slightly different versions of the file it's almost impossible to work out where they should go. A unified diff gives some context before and after each change so that patch has more chance of working out where it goes. To make a unified diff, add the -u option to diff.
#4
A unified diff would definately make reviewing and applying this patch easier.
If you can't provide a unified patch, please reply and post the entire module file that includes the changes. This will make it easier to compare differences in your patch.
For help on creating patches refer to the documentation on Creating Patches.
#5
Could you attach an screenshot of the result??
My nodes are linked to two vocabularies (let's say, type/model of car, and location), so for an image node of a car, I want to have two breadcrumbs, in order to know the location (let's say Spain -> Barcelona -> High Street) and the model ( Audi -> A3 -> A3 1.9 TDI). That will allow the user to know in which categories are, quickly, and also allow the user to browse to "Barcelona" or "A3" quite fast.
I'm not sure if your patch is to display all the breadcrumbs related with the vocabularies you have associated with a node...
#6
Subscribing,
greetings,
Martijn
#7
Sorry I took so long to reply to this - I've been out and about a bit. I've attached the complete code - the changes are made in the settings function and in hook_nodeapi as far as I can remember.
I've also attached an example of the result - using a theme which is based on Box-Grey.
It would be nice to see this get included in the module - is it still being maintained?
#8
Joel,
Yes the module is still being maintained. In fact, I will soon be releasing an improved version which includes improved configuration options; each vocabulary will be individually configurable (currently settings apply to all vocabularies). It also includes better views integration and supports using different views for different vocabularies as well. Many bug fixes and general code improvements have been made as well. I will posting the updated version and further details to each addition in the next couple of weeks.
Also, I am currently working to push out three sites this week so I'm not sure that I will be able to merge this feature into the code base right away. I do think it is a great option and I will be sure that the updated version will include this.
Thanks for the screen shot and hopefully I can review the code shortly.
#9
These sound like amazing new features - looking forward to seeing the new version very much!!
Is there any chance of doing a 'real' release of the new features so it will be flagged by update status as soon as it is available?
#10
Subscribe. This feature would be a killer!
#11
@joel_guesclin: See #4 above
#12
Subscribe!
Is it considered in active development for 5.x or 6.x?