t() in feature messes up translation database

Created on 22 November 2016, almost 8 years ago
Updated 17 January 2024, 10 months ago

I had a real hard time debugging and cleaning my translation tables.

The root cause turned out to be the t()'s in the feature file.
Imho they should not be there as
* for the default textgroup they come from other modules where the t() already is, so are not necessary
* for other textgroups they do real harm, causing a second DB entry like this:
** somefieldname, textgroup=field, context=field:foo:title # good entry
** somefieldname, textgroup=default, context=field:foo:title # evil entry

🐛 Bug report
Status

RTBC

Version

2.0

Component

Code

Created by

🇩🇪Germany geek-merlin Freiburg, Germany

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024