Problem/Motivation

When the Drupal 11.3.2+ build is ready, it needs testing.
Use this as a stub issue for the related regression issues with fixes.

Steps to reproduce

Upgrade an existing WxT from 6.2.x to 6.3.x and test the upgrade.
Install a fresh WxT 6.3.x site and test it.
Log issues and add related issues to this ticket.

Proposed resolution

See problem/motivation.

Remaining tasks

Create the WxT 6.3.x branch and update the build for D11.3.2+

User interface changes

Minimal

API changes

Some new deprecations expected.

Data model changes

Minor changes.

Comments

joseph.olstad created an issue. See original summary.

joseph.olstad’s picture

joseph.olstad
Primary language French
commented
Status: Active » Postponed
Parent issue: » #3572653: WxT 6.3.x

Postponing on #3572653: WxT 6.3.x

smulvih2’s picture

smulvih2
Location Canada 🍁
commented
Version: 6.2.x-dev » 6.3.x-dev
Status: Postponed » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

joseph.olstad’s picture

joseph.olstad
Primary language French
commented
Assigned: joseph.olstad » Unassigned

Looks good.

Breadcrumb behavior changed at some point between us running wxt 6.1.x in production and upgrading to wxt 6.2.x. The menu_breadcrumb module is likely where the change happened. Ended up handling a few edge cases in a hook in order for pages that do not have menu links and or are not node pages to have a current page breadcrumb item.

with that said, depending on the configuration options used, depending on what your dept expects from breadcrumbs you may or may not notice this issue.

Our projects automated testing picked up the differences. WxT automated tests probably don't cover the non menu breadcrumb node breadcrumbs or have a different default setting.

Status: Fixed » Closed (fixed)

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