The Calendar plugin has an issue with non-English languages. srosset81 reported that when creating an event, the plugin adds the code allowedGroups="trust_level_0" which doesn’t work because the group name is translated to the local language (e.g., “niveau_confiance_0” in French). This prevents users from creating events.
However, renato couldn’t reproduce the issue and suggested that the problem might be related to the visibility of the automatic groups. They noted that the user creating the event must be able to see the groups defined as allowed groups.
srosset81 later confirmed that the issue was indeed related to the visibility of the automatic groups and that changing it to “all logged users” solved the problem.
Jagster mentioned that this issue might be related to a long-standing problem with non-English automatic groups, but renato disagreed, stating that the plugin works fine in non-English communities, including their own Brazilian Portuguese community.
If you are installing Discourse in another language, the “trust levels” groups will have a different name. For example in French, instead of “trust_level_0” you will have “niveau_confiance_0”.
Now if you create an event with the Calendar plugin, and you want your event to be public, it will add this code: allowedGroups="trust_level_0". Except there is no “trust_level_0” group so all users get a “Invalid allowed groups” error.
The plugin is thus not usable at all by non-English users.
Is there a way to go around this bug quickly ? I just moved a community to Discourse and all users are being blocked from creating events because of this bug. Unfortunately I cannot rename “niveau_confiance_0” to “trust_level_0”, as it is an automatic group. Or maybe this can be done somewhere directly in the settings ?
This has been an issue for long time now and affects for example using of tag groups.
Nothing has changed so I guess the team has painted themselves on the corner at some point. And that’s why they can’t use english form internally, inside the code, and other languages outside on the UI.
But I’m just guessing, because no one has told what are the actual difficulties to fix this. Or I’ve missed the reasoning, that is possible too.
Sorry, I can’t reproduce this issue. Any of the original English names in automatic groups is valid here as allowedGroups.
Note, however, that the user creating the event must be able to see the groups defined as allowed groups. Did you happen to change these visibility levels for your automatic groups?
Thanks, the visibility was limited to the group owner, and changing it to all logged users solved the problem indeed ! Sorry for making bold assumptions, I didn’t explore the problem long enough.
