- Issue created by @joseph.olstad
- Merge request !86Issue #3525363 by joseph.olstad: Upgrade from Drupal 10.4.7 to Drupal 11.1.7... β (Merged) created by joseph.olstad
- π¨π¦Canada joseph.olstad
Helps if the patch has the correct issue number
I followed the repro steps on a fresh drupal install with core 10.4.7. Then installed book module, did not create any book nodes. Upgraded to core 11.1.7. Could not reproduce. Is there another step here?
- π¨π¦Canada joseph.olstad
unset your allowed types somewhere before upgrading to D11
$this->configFactory->get('book.settings')->set('allowed_types', NULL)));
I'm not sure why this allowed_types was NULL in my case, I didn't change this explicitly but to reproduce it is involved.
I'll possibly circle back with a better explanation later.
- π¨π¦Canada Liam Morland Ontario, CA π¨π¦
liam morland β made their first commit to this issueβs fork.
- π¨π¦Canada Liam Morland Ontario, CA π¨π¦
I have added the changes needed to fix
book_type_is_allowed()
. - π¨π¦Canada Liam Morland Ontario, CA π¨π¦
Until the deprecated function is removed, it needs to be fixed.
-
smustgrave β
committed 8bf9cbbf on 2.0.x authored by
joseph.olstad β
Issue #3525363 by joseph.olstad: Upgrade from Drupal 10.4.7 to Drupal 11...
-
smustgrave β
committed 8bf9cbbf on 2.0.x authored by
joseph.olstad β
- πΊπΈUnited States smustgrave
Will merge into 2.0.x, though setting it to a null value seems like someone did a bad drush command. Not reproducible without actively trying to do something incorrect.
- π¨π¦Canada Liam Morland Ontario, CA π¨π¦
Thanks!
This could also happen if
book.settings
is deleted entirely. Someone trying to reset things might do that. -
smustgrave β
committed e986bd87 on 3.0.x
Issue #3525363 by joseph.olstad, liam morland, mdranove, smustgrave:...
-
smustgrave β
committed e986bd87 on 3.0.x
Automatically closed - issue fixed for 2 weeks with no activity.