Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: Set subscribe option in event itself not only in archive global #46

Open
Kahmoon opened this issue Jul 22, 2020 · 9 comments

Comments

@Kahmoon
Copy link

Kahmoon commented Jul 22, 2020

Hi Kamil,

actually i faced a problem where i wanted an event not be able to subscribe. But actually its only possible to enable/disable subscriptions global in archive settings.

When i disable subscribing in calendar archive, its not possible to create events with subscriptions anymore.

So its actually not possible to make a normal event without subscription.

There should be an option in the event itself for subscribing enabled or not. Actually you just can override settings if its enabled globally.

Greetings Frank

@Kahmoon
Copy link
Author

Kahmoon commented Aug 12, 2020

Any solution for this so far? :-P

@Aybee
Copy link
Contributor

Aybee commented Aug 14, 2020

Two situations:

  1. Almost every event should be subscribable
    Calendar settings: activate subscribe
    Event settings: overwrite a few exeptions (done by using a dummy member group authorization or guests only, depending on your concept)
    State: works

  2. In principle, events should not be subscribable.
    Calendar settings: activate subscribe
    Event settings: overwrite almost all events (done by using a dummy member group authorization or guests only, depending on your concept)
    State: works (but not comfortable)
    Should be:
    Calendar settings: activate subscribe
    Event settings: overwrite almost all events (done by deactivating a checkbox)
    State: Feature Request

Would that be in your interest?

Yes, I can imagine that this would be useful. Can also be used in situation 1..

@Kahmoon
Copy link
Author

Kahmoon commented Aug 14, 2020

Using a dummy user group would not be a good solution because we have an output in the templates for events to which other usergroups can register.

For Example: Event abc can only be subscribed by class x, y when i am in user group z

Disabling subscribing to specific events at all would be the best solution. Then nothing of subcribing is shown one the website and nobody gets confused.

@Aybee
Copy link
Contributor

Aybee commented Aug 14, 2020

For Example: Event abc can only be subscribed by class x, y when i am in user group z

???

@Kahmoon
Copy link
Author

Kahmoon commented Aug 14, 2020

Actually we have calendar archives for each class and one archive for all classes.

For events in "all classes" you have to choose in Eventsettings which class can subscribe. Every other class can see this event, but cannot subscribe. In those events there is a hint, which is generated automatically from the settings:

Dieser Termin ist nur für folgende Kurse: München 2019-11, München 2020-01, München 2020-03

A workaround with a dummy class would also output this text. It would be better to disable registration at all, because not every events needs a subscribe option. Actually this is not possible.

@Kahmoon
Copy link
Author

Kahmoon commented Aug 25, 2020

Hi Kamil,

may i bump here again? :-)

@amimoto1
Copy link

A possible workaround to disable the subscription of single events without any programming could be setting a "Subscribe end time" of a few years before the event.

@Kahmoon
Copy link
Author

Kahmoon commented Aug 31, 2020

Edit: Sorry....no negative value needed :-)

But not a nice solution anyways :(

@Kahmoon
Copy link
Author

Kahmoon commented May 19, 2021

May i bump this? No one else is missing this feature? :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants