Breadcrumb API

[Apiweb]

I think a cool addition to WordPress, as well as the menus and widgets, would be an API for Breadcrumb so the pages, posts, categories, themes and plugins might use this API and so have a breadcrumb more consistent across the entire environment WordPress .

[SergeyBiryukov]

Previously: #4861. Related: #21506.

Sounds like plugin territory to me. Should probably be suggested as a ​feature plugin first.

[helen]

Agree with plugin territory. Demand for it in core has not been noticeable. As always, welcome to re-open later, but would do the plugin thing first.

[Apiweb]

Replying to helen:

Agree with plugin territory. Demand for it in core has not been noticeable. As always, welcome to re-open later, but would do the plugin thing first.

Quick question, did not understand why he is plugin. I would change the core. Since WordPress itself would provide an API for Breadcrumbs, where themes and plugins might use it, as with Menus and Widgets.
Would not a plugin, but something that the very core of WordPress would provide.

[chipbennett]

I'm going to submit a patch for this, under a different ticket (I don't think an API is needed; just a core template tag).

Over the past four years reviewing Themes, I have seen the breadcrumb navigation wheel re-invented many times over by Theme developers. Breadcrumb navigation is standard template functionality. Non-core solutions are sub-optimal, IMHO. Not having a core template tag for breadcrumb navigation forces Theme developers either to rely on a Plugin for basic template functionality, or else develop custom code for a very common feature. Relegating breadcrumb navigation to Plugin territory would be analogous to saying paginate_links() or posts_nav_link()/previous_posts_link()/next_posts_link() are Plugin territory.

[SergeyBiryukov]

#31649 was marked as a duplicate.

[cardiganmedia]

Template tag for standardizing breadcrumb navigation

[cardiganmedia]

Just attached a patch from my duplicate feature-request ticket.

[wlindley]

Submitted patch has extra, unclosed <div> in the 'page' handler. I suggest this function, if in core, should return a list of hashes, in the same format as get_bookmarks(), and let the plugin/theme handle any desired HTML generation. I have suggested a modification of the patch to @cardiganmedia.

[cardiganmedia]

I'm tweaking this patch a bit -- adding an option to return or echo, and streamlining some code. I'll upload the new version tonight.

[cardiganmedia]

I've made a few tweaks to clean things up a bit, and also added an echo argument for better user control, as well as a filter (wp_breadcrumb_args) for argument filtering.

[cardiganmedia]

New version of breadcrumbs template tag

[wlindley]

What about the case where a Page sits several below levels of parents; shouldn't this walk the tree of parents until we get to root? That could be parent = 0 or, if ('page' == get_option('show_on_front')) then the root page's id is get_option('page_on_front').

[cardiganmedia]

Will have a new patch with full ancestor path by tomorrow. I'm still testing things.

[cardiganmedia]

New version that builds the full path for pages. I'd love to see input from others regarding possible improvements here.

[swissspidy]

No movement in over 15 months and a clear suggestion to use a plugin instead (and perhaps making a feature project out of it).