Skip to content
This repository has been archived by the owner. It is now read-only.
experience edited this page Oct 13, 2012 · 2 revisions

Super simple

If you use standard ExpressionEngine template_group/template/entry URLs, just add the Crumbly tag to your templates, and you're done.

The same goes for ExpressionEngine categories (category names or IDs), and even Pages URLs. Crumbly is smart enough to recognise and handle them, straight out the box.

What used to require lots of messy ExpressionEngine conditionals, and multiple section-specific includes, now takes minutes.

Endlessly configurable

But what if you're removing the template from the URL, or appending additional segments?

Not a problem.

Crumbly lets you specify custom URLs patterns, which it uses to parse the page breadcrumbs. Want to omit a particular segment? Easy. How about ignoring all trailing segments? Piece of cake.

{exp:crumbly:breadcrumbs
    custom_url:pattern='template_group/entry/glossary/ignore/entry'}

You name it

Crumbly's settings screen makes it easy to assign custom labels to template groups and templates. You can even create your own glossary, for use with custom URL segments.

Now you can transform that boring old hotels template group into the considerably more exciting "Transient Accommodation Unit" breadcrumb. Much better.

Effortless integration

Crumbly's template tag is super-easy to use. Just add it to your template, and you have instant, easy access to the target URL, segment, and label for every step along your breadcrumb path. Hansel and Gretel never had tools like this.

{exp:crumbly:breadcrumbs}
    {if count < total_results}<a href="{breadcrumb_url}">{/if}
    {breadcrumb_title}
    {if count < total_results}</a>{/if}
{/exp:crumbly:breadcrumbs}
You can’t perform that action at this time.