drush updb fails on 4.4.2/ 4.5.0 and possibly 5.0.x on last updb 4.2.0 -> 4.3.4 -> 4.5.0

Created on 21 March 2023, over 1 year ago
Updated 13 October 2023, about 1 year ago

Problem/Motivation

Patch from here didn't make it

https://www.drupal.org/project/wxt/issues/3340061

Steps to reproduce

Proposed resolution

Make sure this patch goes in:

https://www.drupal.org/project/wxt/issues/3340061

🐛 Bug report
Status

Closed: outdated

Version

4.5

Component

Code

Created by

🇨🇦Canada joseph.olstad

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

Comments & Activities

  • Issue created by @joseph.olstad
  • 🇨🇦Canada sylus

    Hi @joseph this patch wasn't needed because it was only fixing a symptom of the problem and is why I did a hotfix release v4.4.2.

    I mentioned in a comment that it was fixed in 4.4.2 because the blocks call was happening before the new menu system is in place.

    ---

    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 myself when working on upgrade path 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();

  • Status changed to Closed: works as designed over 1 year ago
  • 🇨🇦Canada sylus

    Maybe you ran the hook_update_n when were on 4.4.1 so is why you still saw the problem.

  • 🇨🇦Canada smulvih2 Canada 🍁

    @sylus agreed, 4.4.2 fixes the issue for me. I just did an upgrade last night to 4.4.2 and it worked as expected.

  • 🇨🇦Canada joseph.olstad

    it wasn't me, it was someone who reached out to me about this issue, I'll let him chime in, however I had him upgrade from 4.2.0 to 4.3.4 then to 4.5.0,
    4.4.1 was skipped.

  • Issue was unassigned.
  • Status changed to Active over 1 year ago
  • I am working on Windows server 2019. PHP 8.19
    I cant upgrade past 4.3.4
    i still have the same error below when trying to upgrade all wxt version 4.4.0 4.4.1 4.4.2 4.5.0
    drush updb error below

     [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 profiles/wxt/modules/custom/wxt_core/src/ConfigHelper.php on line 104
     [error] Update failed: wxt_core_update_8441`
  • Status changed to Postponed: needs info over 1 year ago
  • 🇨🇦Canada sylus

    @momo445566 you were likely on 4.4.1 and ran the drush updatedb, can you switch to 4.4.2 and set back the drush update hook so it runs again?

    Maybe even clear the cache?

    This error has been fixed in 4.4.2 and tested across a few sites without issue by myself and a few others.

    Can u paste right now before doing anything the contents of wxt_core_update_8441?

  • 🇨🇦Canada joseph.olstad

    @sylus could this be due to the fact that he's upgrading to 4.3.4 first, prior to upgrading to 4.4.2?

    lightning was completely removed from the composer in 4.4.0 so therefore the 4.3.4 needs to run first unless doing workarounds like I did putting in fake lightning* modules to fool drupal into uninstalling them.

    there's likely an api way to work around this also.

  • Status changed to Closed: outdated over 1 year ago
Production build 0.71.5 2024