- Issue created by @dbielke1986
- πΊπΈUnited States smustgrave
Did you run drush updb? Not able to replicate
- π©πͺGermany dbielke1986
Yes, updatedb was running successfully.
Can I provide you any further information to get the issue analyzed? - Merge request !97Issue #3531800 by dbielke1986, smustgrave: 'show_top_item' is not a supported key β (Merged) created by smustgrave
- πΊπΈUnited States kwiseman
I was having the same issue after upgrading from 1.0.0 to 2.0.1, even after updating the database. I applied the changes from the merge request as a patch, and that solved it.
- πΊπΈUnited States smustgrave
Will deploy this tonight when Iβm back in front of my computer
-
smustgrave β
committed 3cbc322b on 2.0.x
Issue #3531800 by dbielke1986, smustgrave: 'show_top_item' is not a...
-
smustgrave β
committed 3cbc322b on 2.0.x
-
smustgrave β
committed a8ee2cb7 on 3.0.x
Issue #3531800 by smustgrave, dbielke1986, kwiseman: 'show_top_item' is...
-
smustgrave β
committed a8ee2cb7 on 3.0.x
- π©πͺGermany dbielke1986
Is working fine! No errors anymore.
Thank you for the quick fix and release @smustgrave
- π¬π§United Kingdom AndyF
Hey, I think there's an issue with the
hook_update_N()
that was committed. From the docs, it's safe to use\Drupal::configFactory()->getEditable()
and\Drupal::config()
, as long as you make sure that your update data matches the schema, and you use the$has_trusted_data
argument in the save operation.(my emphasis)
Thanks!