Drush updatedb fails on 4.4.1

Created on 7 February 2023, almost 2 years ago
Updated 13 October 2023, about 1 year ago

Hello!

We run 4 DrupalWxt sites and get the following error when trying to update them to 4.4.1 from 4.4.0. Specifically this error arises at the "drush updatedb" step

> [notice] Update started: wxt_core_update_8441
> [error] Drupal\Core\Config\Entity\ConfigEntityStorage::createFromStorageRecord(): Argument #1 ($values) must be of type array, bool given, called in /var/www/html/profiles/wxt/modules/custom/wxt_core/src/ConfigHelper.php on line 104
> [error] Update failed: wxt_core_update_8441

🐛 Bug report
Status

Fixed

Version

4.5

Component

Code

Created by

🇨🇦Canada kevin.bruner

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @kevin.bruner
  • 🇨🇦Canada vedla

    The issue is triggered if you have removed any or all of the default wxt blocks.

    I have created a patch that allowed me to run the updates.

  • 🇨🇦Canada sylus

    Oh no :( I forgot to change the order because the blocks can't be created without the new menu system in place.

    I did actually get that error and I fixed it with this:

      // Add the new configuration items for the new GCWeb global footer.
      $config = Config::forTheme('wxt_bootstrap')->optional();
      $config->getEntity('menu', 'footer-contextual')->save();
      $config->getEntity('menu', 'footer-contextual-fr')->save();
      $config->getEntity('menu', 'footer-top')->save();
      $config->getEntity('menu', 'footer-top-fr')->save();
      $config->getEntity('block', 'wxt_bootstrap_footer_contextual')->save();
      $config->getEntity('block', 'wxt_bootstrap_footer_contextual_fr')->save();
      $config->getEntity('block', 'wxt_bootstrap_footer_top')->save();
      $config->getEntity('block', 'wxt_bootstrap_footer_top_fr')->save();
    
    • sylus committed 79dd557d on 4.4.x
      Issue #3340061 by vedla: Drush updatedb fails on 4.4.1
      
  • Status changed to Fixed almost 2 years ago
  • 🇨🇦Canada sylus

    I pushed out v4.4.2 please let me know that this fixes your issue :)

  • 🇨🇦Canada joseph.olstad

    On a fresh install of wxt 4.4.2 I'm getting this error:

    Drupal\Component\Plugin\Exception\PluginNotFoundException: Unable to determine class for field type 'entity_reference_revisions' found in the 'field.storage.block_content.field_carousel_item' configuration in Drupal\field\FieldStorageConfigStorage->mapFromStorageRecords() (line 167 of core/modules/field/src/FieldStorageConfigStorage.php).

    I'll retry the install , this time skipping the Carousel component.

  • 🇨🇦Canada joseph.olstad

    I'm using this:

    commit 31e2fd387cc47fc74eeebf70aa8f94e8cdb49b9f (HEAD, tag: 4.4.2, origin/9.4.x)
    Author: drupalwxt-svc <development+drupalwxt@zacharyseguin.ca>
    Date:   Wed Feb 8 02:00:29 2023 +0000
    
        Update to latest version of WxT 4.4.2
  • 🇨🇦Canada joseph.olstad

    @sylus, confirmed wxt_ext_carousel is where the issue comes.
    Re-installing and then EXCLUDE the wxt_ext_carousel , I am able to install without error after re-installing provided it is without the wxt_ext_carousel module.

  • 🇨🇦Canada joseph.olstad

    A couple things I noticed with a fresh install of 4.4.2

    The mega menu cdn when enabled seems to be either missing some markup or has some weird css issue.

    Secondly, I noticed there's no suggested footer cdn value and when this is disabled there's no longer a mid footer menu.

    Perhaps I have to add menu links into that menu.

    https://wxt.9pro.ca

    also I was adjusting settings without the mega menu cdn, added a landing page node , assigned a menu link for it under the 'home' menu link, the dropdown showed up, but now for some reason it's gone, I am having issues finding the original behavior.

    With that said, something weird with the cdn mega menu, maybe related to the footer cdn changes?

  • 🇨🇦Canada joseph.olstad

    looks like a 4.4.2 fresh install is working well overall except the wxt_ext_carousel and mega menu cdn

  • 🇨🇦Canada smulvih2 Canada 🍁

    @joseph I just did a fresh install of WxT 4.4.2 with all extensions enabled and I didn't run into any issues. I am running on latest the docker-scaffold setup (9.4.x) which uses PHP8.1. I also uninstalled and re-enabled the wxt_ext_carousel via the UI and didn't run into any issues.

    Also enabled the mega menu CDN on fresh install and it works as expected, at least it visually looks and behaves properly.

  • 🇨🇦Canada joseph.olstad

    @smulvih, my environment is php 8.0.22 with Fast-CGI , are you using fpm? I could try fpm and see, I'll switch to php 8.1 and try again.

  • 🇨🇦Canada smulvih2 Canada 🍁

    Yes, the latest docker-scaffold uses php-fpm.

  • 🇨🇦Canada smulvih2 Canada 🍁

    Just updated one of my projects from 4.4.0 to 4.4.2 (including wxt_core_update_8441) and it worked with no issues.

  • 🇨🇦Canada joseph.olstad

    Hmm, ok, my FPM for 8.1 / 8.0 isn't fully installed, I'm going to try FastCGI 8.1

  • 🇨🇦Canada joseph.olstad

    ok @smulvih2 , redoing composer.lock with php 8.1 and re-installing with PHP 8.1 using fastCGI and PHP 8.1 is working for me, for some reason the dependencies get messed up for PHP 8.0, probably some issue upstream.

    So, wxt_ext_carousel works for me with PHP 8.1, but if you delete the composer.lock and do a composer install using php 8.0 and re-install, you'll probably see the error. although when I got the error I didn't select ALL of the dependencies, I skipped wxt_ext_group and wxt_ext_search and wxt_ext_sitemap and one or two others not related to carousel

  • 🇨🇦Canada joseph.olstad

    I've enabled the CDN to show you what it looks like on my fresh install, have a look.

  • 🇨🇦Canada joseph.olstad

    ok I figured out the problem with the mega menu cdn, it is a configuration option I tried.

    if you go into
    admin > configuration > wxt > wxt library > select "Toggle horizontal main menu"

    rebuild caches

    then the megamenu looks blue and open

    uncheck this, the megamenu is fixed after a cache rebuild.

  • 🇨🇦Canada joseph.olstad

    4.4.2 looks great for a fresh install, nice work!

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

  • 🇨🇦Canada joseph.olstad

    Hi @sylus, this patch never made it into 4.5.x and 10.0.x
    It is needed

  • Status changed to Fixed over 1 year ago
  • 🇨🇦Canada joseph.olstad

    Needed in 4.5.x and 5.0.x

  • 🇨🇦Canada joseph.olstad

    The commit that was done here didn't fix the problem. I'll roll a new patch

Production build 0.71.5 2024