🇦🇷Argentina @sharif.elshobkshy

Hi.

I'm seeing the same bug on one of the testing environments. This indeed seems to be related to big taxonomy trees.
Additionally, other tickets exist to discuss/address this.

- https://www.drupal.org/project/drupal/issues/2786793 🐛 Notice: Undefined index: depth in Drupal\taxonomy\Form\OverviewTerms Closed: outdated
- https://www.drupal.org/project/drupal/issues/763380 📌 Do not use \Drupal\taxonomy\TermStorageInterface::loadTree() in \Drupal\taxonomy\Form\OverviewTerms::buildForm() Postponed
- https://www.drupal.org/project/drupal/issues/3367182 🐛 Undefined array key "depth" Active

This is definitely an ongoing bug.

Thanks.

Hi.

I'm seeing the same bug on one of the testing environments. This indeed seems to be related to big taxonomy trees.
Additionally, other tickets exist to discuss/address this.

- https://www.drupal.org/project/drupal/issues/3270691 🐛 Undefined index in Drupal\taxonomy\Form\OverviewTerms->buildForm() Closed: cannot reproduce
- https://www.drupal.org/project/drupal/issues/763380 📌 Do not use \Drupal\taxonomy\TermStorageInterface::loadTree() in \Drupal\taxonomy\Form\OverviewTerms::buildForm() Postponed
- https://www.drupal.org/project/drupal/issues/3367182 🐛 Undefined array key "depth" Active

This is definitely an ongoing bug.

Thanks.

I had the same error message (mentioned above) after following the above link document. 

The SQL storage cannot change the schema for an existing field (field_cell in paragraph entity) with data

I'm sure there is a fix/alternative, but with not so much time to dedicate to this task, I ended up:

- Creating a new field.

- Creating a Drush command to migrate all values to the new field.

- In a future deploy, I'll delete the old/original field.

Patch for Domain 2.0.0-beta1 when used in Drupal 10.1.7

sharif.elshobkshy → created an issue.

sharif.elshobkshy → created an issue.

sharif.elshobkshy → made their first commit to this issue’s fork.