- Issue created by @leo liao
- Status changed to Postponed: needs info
8 months ago 9:54am 3 May 2024 Can you confirm that the date format machine name → Y年 is the cause? If so, how did you enter Y年 as a date format machine name?
When investigating webform/src/Plugin/WebformElement/DateBase.php:183, we found that it directly uses DateFormat::load('Y年') for query. In drupal, the format of id has requirements that do not allow the use of '年'. This kind of character.
- Status changed to Needs work
7 months ago 5:34am 14 May 2024 I found two related questions.
https://www.drupal.org/project/drupal/issues/3415478 🐛 \Drupal::entityTypeManager()->getStorage('user_role')->load() can't load non-english string Closed: won't fix
https://www.drupal.org/project/webform/issues/3415445 🐛 Search Chinese in /admin/structure/webform cause error: Illegal mix of collations Closed: duplicate- last update
7 months ago 536 pass - 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
Please put the patch into an issue fork and merge request.
- First commit to issue fork.
- 🇺🇸United States jrockowitz Brooklyn, NY
We need to standardize our approach to special character in config entity id.
The MR also updates 🐛 \Drupal::entityTypeManager()->getStorage('user_role')->load() can't load non-english string Closed: won't fix to use
mb_convert_encoding($keys, 'ASCII', 'UTF-8')
which feels easier to understand thaniconv('UTF-8', 'ASCII//TRANSLIT', $keys)
and both statement accomplish similar goals. - Merge request !563Issue #3443934: Item format custom HTML is not valid → (Merged) created by jrockowitz
-
jrockowitz →
committed 30a15a9b on 6.3.x
Issue #3443934: Item format custom HTML is not valid
-
jrockowitz →
committed 30a15a9b on 6.3.x
-
jrockowitz →
committed 30a15a9b on 6.x
Issue #3443934: Item format custom HTML is not valid
-
jrockowitz →
committed 30a15a9b on 6.x
-
liam morland →
committed b55879c6 on 6.3.x
Issue #3443934: Remove obsolete spelling exception Obsolete since...
-
liam morland →
committed b55879c6 on 6.3.x
-
liam morland →
committed b55879c6 on 6.x
Issue #3443934: Remove obsolete spelling exception Obsolete since...
-
liam morland →
committed b55879c6 on 6.x
Automatically closed - issue fixed for 2 weeks with no activity.