- Issue created by @claudiu.cristea
- First commit to issue fork.
- π΅π±Poland alorenc Wolsztyn, π΅π±
I donβt see a "Skip" button in the UI.
I assume that we need to add a button that will allow the user to change the active value for the selected row. - π΅πΉPortugal saidatom Lisbon
@yaqbick One last note: when translation is disabled, the Save button should be disabled as well. Otherwise, it results in errors.
- First commit to issue fork.
-
huzooka β
committed 83512b04 on 1.x authored by
yaqbick β
Issue #3533693: Skip strings for translation
-
huzooka β
committed 83512b04 on 1.x authored by
yaqbick β
-
huzooka β
committed 27fe51d0 on 1.x
Revert "Issue #3533693: Skip strings for translation" This reverts...
-
huzooka β
committed 27fe51d0 on 1.x
- ππΊHungary huzooka Hungary ππΊπͺπΊ
In this Babel MR, the logic which was added to control the status of the translatable strings is wrong: The code assumes that the
$keys
variable here contains a single plugin key, but it is actually a comma-separated string ofbabel_source
IDs (same string / context pair might be used even by a Locale and also in multiple configuration).I'd like to see the motivation behind this
status
property, mostly to see what it is about.- If status really belongs to a
babel_source
record, we must create another UI which lists those individual records. But, we can also delete thebabel_source_status
table because it does not make any sense. - If status belongs to an actual source string + context pair then most probably we should remove it from the
babel_source
table.
Reverted the commit and at the same time, added the "Needs issue summary update" tag.
- If status really belongs to a