I just found a slight "issue" with the custom paths. They work *awseomely* by the way - thanks!

The system appears to apply the last match... I just manually inserted a batch of custom paths into my paths table..

INSERT INTO custom_breadcrumbs_paths (titles,paths,specific_path) VALUES
("Marketplace", "marketplace", "marketplace/tenders"),
("Marketplace", "marketplace", "marketplace/jobs"),
("Marketplace", "marketplace", "marketplace/facts"),
("Marketplace", "marketplace", "marketplace/people"),
("Marketplace\nSearch By Letter", "marketplace\nmarketplace/people", "marketplace/people/*"),
("Marketplace", "marketplace", "marketplace/peoplemoves"),
("Marketplace", "marketplace", "marketplace/conferences"),
("Marketplace", "marketplace", "marketplace/organisations"),
("Marketplace\nSearch By Letter", "marketplace\nmarketplace/organisations", "marketplace/organisations/*"),
("Marketplace", "marketplace", "marketplace/organisations/category");

(this is for use on a new version of http://www.sportbusiness.com/marketplace/)

Now the last 3 URL's are for the same section. If I inserted them so the "*" one was last, then THAT took precedent over the non-wildcard "category" one.

Maybe there could be a weight column (along with D6's nice drag-and-drop block-like admin page?)... That would help people when then have similar breadcrumb URL's all colliding on similar URL's.

Or - an alternative - maybe non-wildcard URL's should take precedent over wildcard based ones? But then you still have the same issue of URL's containing miltiple wildcards...

Comments

MGN’s picture

MGN commented

Thanks for bringing this up, and sorry for the delayed response.

I agree it becomes an important issue when you use multiple custom breadcrumbs submodules. I like the idea of allowing breadcrumbs to take precedence based on an assigned weight and will look into how that might be implemented.

MGN’s picture

MGN commented
Status: Active » Fixed

I am going with your alternative suggestion.

Weighting of breadcrumbs by breadcrumb type automatically happens because of module weighting.

For paths with wildcards, I agree that precedence should go to the path without wildcards. If there are multiple wildcards, the number of wildcards can be used to determine the precedence. A match with only one wildcard takes precedence over a two wildcard match, etc.

I've now implemented this in the latest commit: http://drupal.org/cvs?commit=257468 .

Thanks again for the suggestion!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.