• Groundworx

    (@alexandrie)


    I really like the Breadcrumbs Block plugin, it’s simple and clean. I’d love to request a feature that would make it even more useful for agency setting:

    1. Primary Category/Taxonomy Control
      It would be great to have the ability to set a primary category or taxonomy term per post (or inherit from something like Yoast or Rank Math’s “primary category”). Right now, it defaults to the first taxonomy term in the list, which isn’t always the one we want displayed in breadcrumbs.
    2. Taxonomy Selection / Disable Option
      Ideally, users could choose which taxonomy to include in the breadcrumb trail — for example, “category” vs. “custom taxonomy.”
      There should also be an option to disable taxonomy display entirely (e.g., show only “Home → Page”).
    3. Global Separator Setting
      The ability to define a global separator in plugin settings would be great for consistency across all Breadcrumbs blocks.
      The per-block override could remain (for flexibility), but having a single global setting would prevent repetitive configuration.

    These changes would make the plugin much easier to integrate into larger sites and improve workflow for developers managing multiple content types.

    Thanks for considering these requests, I really appreciate the work that’s gone into the plugin so far!

Viewing 1 replies (of 1 total)
  • Plugin Author Justin Tadlock

    (@greenshady)

    @alexandrie – Thanks for the feedback! These are great requests.

    For the primary taxonomy control, I added a GitHub issue to explore this: https://github.com/x3p0-dev/x3p0-breadcrumbs/issues/25

    The taxonomy selection/disabling feature is coming in version 4.0.0. I’ve already implemented it on the GitHub repo and am currently testing it. Happy to hear any feedback on how it works if you want to give it a try.

    For the global separator, have you tried to use a pattern? That’s usually the standard method for handling global settings for blocks that you want to be reused everywhere. You could go with a synced pattern. Or if handling this from within a theme template, you could just set the custom parameter there.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.