Merge branch 'master' into feature/automatic-ipn-generation

config/parameters.yaml

@@ -8,7 +8,7 @@ parameters:
 
   # This is used as workaround for places where we can not access the settings directly (like the 2FA application names)
   partdb.title: '%env(string:settings:customization:instanceName)%'  # The title shown inside of Part-DB (e.g. in the navbar and on homepage)
-  partdb.locale_menu: ['en', 'de', 'it', 'fr', 'ru', 'ja', 'cs', 'da', 'zh', 'pl']    # The languages that are shown in user drop down menu
+  partdb.locale_menu: ['en', 'de', 'it', 'fr', 'ru', 'ja', 'cs', 'da', 'zh', 'pl', 'hu']    # The languages that are shown in user drop down menu
 
   partdb.default_uri: '%env(string:DEFAULT_URI)%'             # The default URI to use for the Part-DB instance (e.g. https://part-db.example.com/). This is used for generating links in emails
 

config/permissions.yaml

@@ -24,7 +24,7 @@ perms: # Here comes a list with all Permission names (they have a perm_[name] co
         label: "perm.read"
         # If a part can be read by a user, he can also see all the datastructures (except devices)
         alsoSet: ['storelocations.read', 'footprints.read', 'categories.read', 'suppliers.read', 'manufacturers.read',
-                  'currencies.read', 'attachment_types.read', 'measurement_units.read']
+                  'currencies.read', 'attachment_types.read', 'measurement_units.read', 'part_custom_states.read']
         apiTokenRole: ROLE_API_READ_ONLY
       edit:
         label: "perm.edit"
@@ -133,6 +133,10 @@ perms: # Here comes a list with all Permission names (they have a perm_[name] co
     <<: *PART_CONTAINING
     label: "perm.measurement_units"
 
+  part_custom_states:
+    <<: *PART_CONTAINING
+    label: "perm.part_custom_states"
+
   tools:
     label: "perm.part.tools"
     operations: