Niet-medewerkers kunnen geen agenda-afspraken maken

[marvi]

We are using the Calendar plugin and have tried to enable event posting for all users:

However when non-staff users try to post to the calendar this notice comes up:

Has anyone else experienced this issue? Is it in fact a bug or are we setting something up incorrectly?

[sam (Sam Saffron)]

Oh, dit is inderdaad een vergissing, kun je proberen het in te stellen op trust_level_0, iedereen is een speciale groep en het lijkt erop dat we hier wat speciale afhandeling missen.

trust_level_0 is een groep die elke ingelogde gebruiker op je forum vastlegt.

[Moin]

There is also another topic about this issue

Selecting the "everyone" group in the allowed_on_groups setting does not enable event creation

The discourse post event allowed on groups setting drop down gives the “everyone” group as one of its options. When selected, the expectation is that everyone will be allowed to create events, but this is not the case. To allow any user on the forum to create an event, the trust_level_0 group would need to be selected. [image] I think that similar issues with the “everyone” group being included in settings dropdown menues has come up in the past. Probably the setting is just pulling in all gr…

[kris.kotlarek (Kris)]

This error is displayed in two cases:

1. The user tries to create a private event and invite groups that they cannot access. For example, here I try to invite admins:

To make it work, I would need to change the permission on the Admins group.

2. A private event is clicked, but no groups are specified.

Maybe we should improve the event builder form to inform the user that this is an incorrect configuration.

---

@marvi, is it possible that one of those scenarios happened in your case?

[marvi]

Thank you all for your replies! And interesting about the ‘everyone’ setting. I have updated it to trust_level2, which is the lowest trust level at which people enter, but it’s still not working unfortunately. The events are public and all groups are allowed:

[kris.kotlarek (Kris)]

I took another look and I think I know what is happening. The wizard to build an event is adding this allowedGroups=trust_level_0 to the event for public events.

In most cases, by default, everyone can see the trust_level_0 group, but in your case, it is configured that only Group owners and moderators can see it.

Something similar to my test instance:

Because allowedGroups is mentioned, permission is checked and trust_level_2 members cannot “see” trust_level_0.

I will work on fixing the wizard so that it is not adding “allowedGroups” for public events, as it is unnecessary.

In the meantime, you have 2 options to fix this issue:

1. Remove allowedGroups by hand so your event should look like this:

[event start="2025-08-12 09:49" end="2025-08-13 00:00" status="public" timezone="Pacific/Auckland"]
[/event]

2. Change the visibility of trust_level_0 group to logged on users. You can do this on this page /g/trust_level_0/manage/interaction

I will let you know once the fix to the event wizard is fixed.

[kris.kotlarek (Kris)]

I made a fix for event builder to not add allowedGroups for public events and it was deployed to your instance.

FIX: Remove redundant allowedGroups parameter