Problem/Motivation

We'd like to move to WxT 6.3.x asap and take advantage of the significant improvements provided by Drupal 11.3.2+

Steps to reproduce

See the release notes for Drupal 11.3.0(+).

Proposed resolution

Create a WxT 6.3.x branch from the HEAD of 6.2.x (@smulvih2)
Work on a new 11.3.2+ update (@joseph.olstad & @smulvih2)
See followup D11.3.2+ testing task.

Remaining tasks

See proposed resolution.

User interface changes

Some minor changes are possible.

API changes

Some new api deprecations. Some existing APIs internals have been "optimized".

Data model changes

Might be some minor changes.

Comments

joseph.olstad created an issue. See original summary.

joseph.olstad’s picture

joseph.olstad
Primary language French
commented
Title: D11.3.2+ upgrade and WxT 6.3.x » WxT 6.3.x

I'll try to kick this around myself.

smulvih2’s picture

smulvih2
Location Canada 🍁
commented
Related issues: +#3546341: cannot install the module because unmet dependecy and some field error

In Drupal 11.3.x, field.storage.node.body was moved out of the Node module into a new node_storage_body_field sub-module (#3447617). This caused some issues with sub-module installs that relied on this config, specifically wxt_ext_page and wxt_ext_landing_page. This issue was also seen with the drupal/blog module, I created a patch to fix (see related issue).

Had to update drupal/drupal-extension to fix behat tests in PHP8.4. Also had to patch panels and page_manager to fix PHP8.4 deprecation notices.

We now have a dev release of 6.3.x, will keep this ticket open until we release 6.3.0.

joseph.olstad’s picture

joseph.olstad
Primary language French
commented

ok great work!
I see you fixed #3568049-21: Body field is hidden in the node form for basic page when only installing two sub-modules

awesome!

smulvih2’s picture

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

Just released 6.3.0, closing this ticket.

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

see my comments from #3572651-5: Test Drupal 11.3.2+ with WxT 6.3.x

The main observed differences upgrading from wxt 6.1.x or prior to WxT 6.2.x/6.3.x is pertaining to breadcrumbs (depending on configuration options that may or may not be selected)

Otherwise WxT 6.2.x is better performance than WxT 6.1.x and WxT 6.3.x is vastly better performance than anything we've ever released.

So, the two things that someone may want to pay attention to in acceptance testing of upgrades:

  1. wet-boew form validation and webforms in general, whether or not you use wb-frmvld (ships as an option since WxT 6.2.x), some related twig changes to wxt_bootstrap. I recomment this improvement #3578948: Improvement - Render novalidate on forms that use wb-frmvld
  2. breadcrumbs (depending on configuration)

Documentation links:

Status: Fixed » Closed (fixed)

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