Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I have VAT Number field translated using i18n_field module, but the translations doesn't get applied to the formatter.
Usually i18n_field module takes care of providing translated formatters for fields provided by core and maybe popular contrib modules, but since this module isn't that popular, it could be handled by this module itself.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | i1931520-8.patch | 2.85 KB | attiks |
| #5 | vat_number-i18n_field-1931520-5.patch | 2.96 KB | dwkitchen |
| #1 | 1931520-1.patch | 1.34 KB | iMiksu |
Comments
Comment #1
iMiksuHere you have a patch which uses
valueinsteadvat_numberarray index in the element which therefore gets handled by i18n_field nicely when translating its label and description.Maybe we could consider changing the whole
vat_numberto be in the schema asvalue?Comment #2
iMiksuComment #3
attiks CreditAttribution: attiks commentedThank you!
Comment #4
dwkitchen CreditAttribution: dwkitchen commentedAgreed. Originally there was going to be two values one for the number and a second for the country.
I am working on updating all uses including db to use value instead of vat_number.
Comment #5
dwkitchen CreditAttribution: dwkitchen commentedNew patch with DB change as well.
Comment #6
attiks CreditAttribution: attiks commentedLooks good to me
Comment #7
dwkitchen CreditAttribution: dwkitchen commentedDid your test included upgrading a site with existing data?
Comment #8
attiks CreditAttribution: attiks commentedUpdate didn't work
Comment #9
dwkitchen CreditAttribution: dwkitchen commentedNow commted