No schema for wxt_core.settings

Alternatively, delete modules/custom/wxt_core/config/install/wxt_core.settings.yml; it does not appear to be in use. The only use of admin_only appears to be from wxt4032404.settings.

Consider switching to 5.1.x-dev

#3409755: 5.1.x requires a merge from wxt 5.0.x - countries fix is missing →
I recommend to either switch to 5.1.x-dev instead of 5.1.0 OR make a patch
easiest solution is to switch to 5.1.x-dev
pretty sure this will fix it.

or try patch in comment #5, this is already fixed in 5.1.x-dev

it would be good to tag 5.1.1 to avoid others getting tripped up, this is an annoying bug to hit.

we've fixed this a few times but we forgot to merge 5.0.x into 5.1.0 , it's in 5.1.x dev but not 5.1.0

Would switching fix it? modules/custom/wxt_core/config/install/wxt_core.settings.yml is still there with the same contents but the only schema for admin_only is in wxt4032404.settings, just like in 5.0.x.

I don't understand how the patch could work. I see this in functional tests, which don't run update hooks because they are a fresh site install.

Try applying the patch and re-install

I tried the patch. It did not make any difference. I don't see how it can, since it only changes update hooks and update hooks to not run in functional tests since it is making a new site.

did you try re-running the hook updates after install?

drush ev "\Drupal::keyValue('system.schema')->set('wxt_core', (int) 8501)";
drush updb -y;

see if this helps?

just curious, but ya if this isn't working on a fresh vanilla install, something is missing from the install profile.

I did not re-run the update hooks, but I do not see why it could make a difference because functional tests do not run update hooks.

Hi Liam Morland,
Thanks for testing the vanilla install.

I had a look at a functioning/working wxt 5.1.x build that I have and I do NOT have a wxt_core.settings.yml file.

I suggest applying this patch to your build and apply it to drupalwxt/wxt

What this patch does is removes the wxt_core.settings.yml

I suspect this might fix the glitch.

You'll probably have to re-install to see if this fixes the vanilla install process

Committed and attributed :)

Thanks so much!

That fixed it. Thanks!

Excellent :)

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