Having just started to use your module, I've run into some problems with paths that aren't content, views or taxonomies and where a custom path must be used.
You've enabled support for the wildcard * - but this has very limited use. Therefore it would be very nice, if you could enable support for regular expressions.
To be precise, I need to change the breadcrumb for forum/blogs/[username] and forum/blogs/[username]/[blogname] independently. If I just use * the two rules will overlap.
Comments
Comment #1
MGN commentedIn principle I agree that extending the flexibility in matching paths is a good idea, and will look into how this might be done with regular expressions. As always, patches against the current 6.x-2.x-dev would help speed things along....
The bigger problem of providing custom breadcrumbs for module/menu pages still remains....and I don't think custom_breadcrumbs_paths can do it yet - it only supports nodes and views right now.
From your paths it looks like these pages are forums and forum posts? Are you using the core forum module?
Comment #2
MGN commentedI just realized that this can already be done without regular expressions.
Create two custom breadcrumbs, one for each path.
Use the breadcrumb visibility field to 'turn on' a particular breadcrumb based on the number of url arguments
for the first path : forum/blogs/[username]
specific path: forum/blogs/*
for the second path : forum/blogs/[username]/[blogname]
specific path: forum/blogs/*
I haven't tested this, but it (or something like it) should work. I still have the same questions as in #1 above.
Comment #3
MGN commentedMarking this as fixed because the question was answered. Also, the wildcard support was improved in a previous commit to custom_breadcrumbs_paths so the overlapping rules are now handled properly - if one wildcard is needed to make the match, it will beat out custom breadcrumb that requires two wildcards to match.