Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: Category translation statuses could be more accurate
Status | Resolved |
Add-on / Version | Publisher 2.5 |
Severity | |
EE Version | 3.5 |
BoldMinded (Brian)
May 15, 2017Description: Currently category and phrase translations are auto-created for non-default languages, thus they are set to the default language value in the database until they’re edited. When a category is saved, even if the user did not change the translated value, since it was marked as saved the is_auto value is set to false, thus indicating that its a value the user entered, not an auto-generated value. This instantly sets the translation status to true for all languages, so the status pips are either all false, or all true, no in between.
To-do: Need to find a way to make the translation status more accurate so it works in conjunction with the is_auto value. Perhaps save the old value as well as the new value when posting the form, comparing the two, and cross referencing it with the is_auto value. E.g.
if old == new && is_auto == 1 then is_auto value stays set to 1
if old != new && is_auto == 1, then set is_auto = 0
BoldMinded (Brian)
After implementing I realized this is not a suitable option. Some words do not change across languages, so the phrase may never be marked as translated even though it is.