Calendar plugin needs group visibility

[srosset81 (Sébastien Rosset)]

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 ?

[Jagster (Jakke Lehtonen)]

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.

[renato (Renato Atilio)]

@srosset81

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.

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?

@srosset81

The plugin is thus not usable at all by non-English users.

That’s not true at all. I’ve been using the plugin for years in my Brazilian Portuguese community.

@Jagster

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.

Fix what, exactly?

[Jagster (Jakke Lehtonen)]

This:

Non-english automatic groups don't stick when applied to Tag Group visibility/usability restrictions

If I set the option: “Keywords are visible for everyone, but only the following groups can use them”. …select groups > save > then reload the page or go back into the options later, the two selected groups are no longer displayed. However, the function comes into effect and only these two groups can subsequently assign tags from the group. This can cause confusion for multiple administrators. Is this the way it is supposed to be? Thanks already for the feedback

With or without this issue is connected to that

This topic is just quite similar one.

[srosset81 (Sébastien Rosset)]

@renato

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.