- Issue created by @vidorado
- π©πͺGermany spuky
Thanks for the patch...
I cleaned it up to only have the inteded changes..
you got a lot of redirects in there too...
- πͺπΈSpain vidorado Pamplona (Navarra)
Agg, thanks @spuky, what a mistake!
- Status changed to Needs review
7 months ago 5:37pm 30 November 2023 - last update
7 months ago Patch Failed to Apply - last update
7 months ago Patch Failed to Apply - last update
7 months ago 105 pass, 9 fail The last submitted patch, 6: 3382356-do-not-translate-computed-fields-nor-untranslatable-paragraph-fields-6.patch, failed testing. View results β
- Status changed to Needs work
7 months ago 9:06pm 30 November 2023 - πΊπΈUnited States recrit
this change logically makes sense to me - exclude fields with no storage, exclude computed fields. Per the failed test https://www.drupal.org/pift-ci-job/2816543 β , it looks like some of the automated tests may need to be updated for this change.
- π©πͺGermany Anybody Porta Westfalica
We just wondered why untranslatable paragraphs fields suddenly had translated values. In our case it was a field to set custom classes on the paragraph (mb-none) and after tmgmt translation by a user, the class was suddenly "mb-keine" (German).
Setting priority to Major. The patch LGTM, but I think it needs a tmgmt maintainer to take a look to ensure the logic is correct!