Content
View differences
Updated by Markus Kahl almost 5 years ago
### **Environment**:
Your OpenProject Version: 11.3.1
### **Logs**
```text
translation data {:one=>"1 projekt", :other=>"%{count} projektov", :zero=>"Brez projektov"} can not be used with :count => 2. key 'two' is missing.: translation data {:one=>"1 projekt", :other=>"%{count} projektov", :zero=>"Brez projektov"} can not be used with :count => 2. key 'two' is missing.
```
### **Steps to reproduce:**
1. Create a **work package** custom field
2. Enable it in exactly **2** projects
3. Change the user's language to **Slovene**
4. Go to Administration -> Custom Fields
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/21451/content"></div></figure>
### **Actual Behavior**
You get an internal server error.
### **Expected Behavior**
You should see the custom fields view in Slovene.
## Discussion
This probably boils down to a missing pluralization in the translation for Slovene in particular. The goal here would be both to amend the missing translation and adjust the code so that it does not fail like this in case a translation is missing. It's better to still be able to use the application but with a missing translation than not being able to use it at all.
Your OpenProject Version: 11.3.1
### **Logs**
```text
translation data {:one=>"1 projekt", :other=>"%{count} projektov", :zero=>"Brez projektov"} can not be used with :count => 2. key 'two' is missing.: translation data {:one=>"1 projekt", :other=>"%{count} projektov", :zero=>"Brez projektov"} can not be used with :count => 2. key 'two' is missing.
```
### **Steps to reproduce:**
1. Create a **work package** custom field
2. Enable it in exactly **2** projects
3. Change the user's language to **Slovene**
4. Go to Administration -> Custom Fields
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/21451/content"></div></figure>
### **Actual Behavior**
You get an internal server error.
### **Expected Behavior**
You should see the custom fields view in Slovene.
## Discussion
This probably boils down to a missing pluralization in the translation for Slovene in particular. The goal here would be both to amend the missing translation and adjust the code so that it does not fail like this in case a translation is missing. It's better to still be able to use the application but with a missing translation than not being able to use it at all.