Closed (fixed)
Project:
Web Experience Toolkit
Version:
6.3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
16 Jan 2026 at 22:58 UTC
Updated:
27 Mar 2026 at 03:40 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
web247 commentedComment #3
web247 commentedHi @joseph.olstad , I don't see this issue myself, perhaps this only happens when you apply the "book restore" patches in the issue #3554907: restore and enhance book solution to wxt-6.3.x ?
Comment #4
web247 commentedNevermind, I was able to replicate the issue by selecting only the "Landing Page" and "Page" modules during the installation:
Comment #5
web247 commentedI created a rough patch that displays the body field and the lead title for the "Basic Page" content type, I tested it myself and seemed to work, please review.
Comment #6
web247 commentedComment #7
joseph.olstadgreat, thanks for the patch @web247!
Comment #8
web247 commentedNo worries !
Comment #9
web247 commentedComment #10
joseph.olstadThis looks like the correct fix.
Comment #11
joseph.olstadI noticed this bug again in a fresh 6.2.0 install.
Therefore just ran a partial import with the patched configuration and it does indeed fix the missing body field , therefore during installation I have a high confidence that this is the correct solution.
Steps:
Apply patch to the html/profiles/wxt
then run a partial config import
drush cim -y --partial --source=profiles/wxt/modules/custom/wxt_ext/wxt_ext_page/config/optionaOnce this is done, the body field shows up on the basic page node form on a fresh installation.
Comment #12
joseph.olstadI recommend committing the changes into the 6.2.x branch since very few will do fresh installs on 5.6.x at this time we can focus on 6.2.x/6.3.x
Comment #13
joseph.olstadsorry meant @smulvih2
Comment #14
smulvih2This is not the right approach. Look at the patch file, it just removes the field_byline, doesn't even mention the body field. This patch essentially removes the byline feature.
Instead, look at the byline field config files, they have a dependency on
taxonomy.vocabulary.departmentswhich is added bywxt_ext_taxonomy. Thewxt_ext_taxonomymodule is not a dependency onwxt_ext_page, so if you only selectwxt_ext_pagethenwxt_ext_taxonomyis not installed, causing the field_byline to fail, causing other issues with the page content type.I suggest looking at how to fix the root cause of this config issue instead of removing fields.
Comment #15
smulvih2Comment #16
joseph.olstadah ok haha, ya helps to actually look at the patch.. strange why it works, I applied it and then the body field shows up after install or even on a partial config import.
Comment #17
joseph.olstadhmm, thanks for the insight, I always select wxt_ext_taxonomy. I'll make sure wxt_ext_taxonomy gets installed correctly. Perhaps an explicit dependency needs to be set here.
Comment #18
smulvih2FYI - in Drupal 11.3,
field.storage.node.bodywas moved out of the Node module into a newnode_storage_body_fieldsub-module (#3447617). So for 6.3.x we need to make node_storage_body_field a dependency on wxt_ext_page and wxt_ext_landing_page in order to have them work as intended by this ticket.Comment #19
smulvih2This took a bit longer to fix based on the change to Drupal core outline in comment #18. This is now fixed, now when you ONLY install
wxt_ext_pageandwxt_ext_landing_pageyou get the body field and all config imports as expected. It also works when all sub-modules are enabled.Here is the commit with the fix for reference - https://github.com/drupalwxt/wxt/commit/6b121967d47fd4155dbeeab7650570eaccec0b69
Comment #22
smulvih2