- Issue created by @iSampo
- 🇫🇮Finland iSampo
Here's a patch that uses the
MetatagsFieldProcessor
for themetatag_computed
field as well. While it does get rid of the extra translation exports, it's likely possible that there is some better solution than this one. - Status changed to RTBC
7 months ago 1:47pm 8 November 2023 - last update
7 months ago 118 pass - 🇦🇺Australia elgandoz Canberra
Thanks for the patch, I had the same patch and this works nice form me, using D10.1.6 and tmgmt 8.x-1.15.
- last update
5 months ago 116 pass, 2 fail - 🇫🇷France NicolasGraph Strasbourg
I think the metatag_computed field should not even be translatable as it is set as computed.
Here is a patch setting computed field as not translatable inContentEntitySource::extractTranslatableData()
. - Status changed to Needs work
5 months ago 2:42pm 24 January 2024 - 🇫🇷France NicolasGraph Strasbourg
Moves to "Needs work" as it would require a test.
- 🇫🇷France NicolasGraph Strasbourg
I guess we could even close it as a duplicate of https://www.drupal.org/project/tmgmt/issues/3405309 🐛 Computed fields should not be embeddable fields or source suggestions Needs review if nobody have objection.
- 🇪🇸Spain rvilar Montcada i Reixac, Catalonia
Using tmgmt version 1.15 and metatags 2.0.0 and it does not work for me. I can see a lot of "meta" strings to translate
- 🇪🇸Spain rvilar Montcada i Reixac, Catalonia
After asking for some channels, pcambra asked me to use both patches in the issue because they are doing differents things. So I can confirm installing both patches fixes the issue.