- Issue created by @lvthunder
- π³πΏNew Zealand quietone
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies β .
I tested this on Drupal 11.x and was not able to reproduce the problem.
- π¬π§United Kingdom catch
From the backtrace this looks like an issue in the field_default_token module.
- π¨πSwitzerland michΓ¨le
I have the same problem as soon as I try to save a new field (regardless of whether I enter a default value or not).