- Issue created by @rcodina
- 🇨🇦Canada nicole.harnish Halifax
Confirmed bug also with:
Drupal 10.3.2
metatag_async_widget 1.2
metatag 2.0I have many sites using this, hoping for an update soon
- 🇺🇸United States rkelbel48
Can confirm, we've had the same issue. This is definitely critical and needs immediate attention.
- First commit to issue fork.
- Merge request !7fix: Keep customized metatags configuration based on the current entity field stored values → (Merged) created by krystianbrzoza
- Status changed to Needs review
4 months ago 9:45am 17 December 2024 - 🇫🇷France nicodh
Hi!
Thanks, the merge request seems to fix this issue (commit 3e411123) on a staging project, I will try on other projects and let you know. - 🇫🇷France nicodh
I've got 3 warnings when saving without opening metatags:
Warning: Undefined array key "value" in Drupal\metatag_async_widget\Plugin\Field\FieldWidget\AsyncMetatagFirehose->massageFormValues() (line 227 of modules/contrib/metatag_async_widget/src/Plugin/Field/FieldWidget/AsyncMetatagFirehose.php).
Warning: Undefined array key 0 in Drupal\metatag_async_widget\Plugin\Field\FieldWidget\AsyncMetatagFirehose->massageFormValues() (line 227 of modules/contrib/metatag_async_widget/src/Plugin/Field/FieldWidget/AsyncMetatagFirehose.php).
Warning: Trying to access array offset on value of type null in Drupal\metatag_async_widget\Plugin\Field\FieldWidget\AsyncMetatagFirehose->massageFormValues() (line 227 of modules/contrib/metatag_async_widget/src/Plugin/Field/FieldWidget/AsyncMetatagFirehose.php).
- 🇵🇱Poland krystianbrzoza
@nicodh
Can you provide any steps to reproduce warnings ? - 🇨🇦Canada Charlie ChX Negyesi 🍁Canada
Smartsheet confirms #15.
This comes up when there are no metatags for the entity in question.
- First commit to issue fork.
- 🇺🇦Ukraine Panchuk Volyn, Lutsk
I can confirm that changes in MR #7 are resolving the problem described above. It is worth merging and releasing a new version ASAP (or at least adding related details on the module page).
- Status changed to RTBC
about 1 month ago 8:24pm 26 February 2025 - 🇩🇪Germany hctom
+1 for the fix. We also encountered this issue on one of our projects... unfortunately AFTER having already lost tons of customized meta tag data :(
@alexpott Can you please provide a new release with this critical fix as soon as possible, so no other users will run into this problem and loose their data as well. Thanks!
- 🇺🇸United States jsutta United States
+1 for a new release ASAP. We lost custom metadata for hundreds of pages and had to reconstruct it with a mixture of scripts and manual work.
-
alexpott →
committed 6092145b on 1.1.x authored by
krystianbrzoza →
Issue #3479093 by krystianbrzoza, rcodina, alexpott, ghost of drupal...
-
alexpott →
committed 6092145b on 1.1.x authored by
krystianbrzoza →
Automatically closed - issue fixed for 2 weeks with no activity.
