[nodebb-plugin-calendar] Fully featured calendar plugin for NodeBB - Testers needed
-
@azeus okay I've identified the issue. I've fixed it on my end but it requires a change to core. It only occurs if you have the "only main post" setting on in the ACP, so you should be fine if you turn that off.
-
@PitaJ said in [nodebb-plugin-calendar] Fully featured calendar plugin for NodeBB - Testers needed:
turn that off.
Tks a lot for the quick fix
"only main post" is a very useful feature but we can live without 
For our usage, the plugin is now almost perfect, the only missing thing is to set a max # of attendees for an event ^^Tks a lot anyway for your great work.
-
set a max # of attendees for an event
Can you give some context for what exactly your use case is? I'm thinking about implementing this next, and having some context will allow me to determine the ideal implementation.
-
@evoixmr It's in my plan. It's just a very large undertaking, and I haven't figured out exactly the best way to implement it within my existing architecture. That's why I'm focusing on smaller issues at the moment.
Have you tested the latest version? I'd like to know if email notifications are working.
-
@PitaJ said in [nodebb-plugin-calendar] Fully featured calendar plugin for NodeBB - Testers needed:
hat's why I'm focusing on smaller issues at the moment.
Have you tested the latest version? I'd like to know if email notifications are working.I didn't tested the email notification yet. I'll do and let you know
-
@PitaJ I'm still having an issue with your plugin, I keep having the restart required on the dashboard.
I also have issue with the master branch, giving an error - The following plugins may not be compatible with your version of NodeBB. nodebb-plugin-composer-default.
Everytime I restart. nodebb stop running, I have to delete the items that was created by "custom static pages - plugin", before I can start using the terminal.
I switched back to branch 1.2.1
-
@evoixmr well the restart required bug is annoying but not really too much of an issue. Regardless, I've identified the issue and I will fix it.
The custom pages thing looks like a real problem, you should probably submit an issue on the repository for it.
-
New version. Please update to
[email protected]if you're willing to run the master branch.npm install nodebb-plugin-calendar@latestChanges:
- Fix "restart required" always showing when plugin is activated
- Improve internationalization
- Edit
invalidevents by hitting the button in the composer
-
@azeus great! If you have any recommendations for improving the email format, let me know.
Also, do you mind describing your use case for limiting the number of attending users? I'm not sure what the purpose is, and knowing that would help me figure out how to best implement it.
-
@PitaJ said in [nodebb-plugin-calendar] Fully featured calendar plugin for NodeBB - Testers needed:
and knowing that would help me figure out how to best implement it.
Sure, actually it's a key feature for us. Our users organise photo events and they like to limit the number of attendees depending of the event. For example, I want to organise an event which is a photo shooting in a photo studio, the max number allowed in the studio is 6 people. I wan't to put 6 as max. So the first 6 users that will subscribe to the event will have the right to participate... The other will maybe subscribe to a waiting list, in case one of the 6 confirmed cancel his participation.
At the moment we need to handle manually the max number. Not sur if I'm clear enough ?
-
@azeus okay. That's what I thought: first come first serve.
Now I just have to figure out how to best add this. I'm thinking maybe changing the response system in a "maximum attendees" event to something like this:
Nis max # of attendees- If less than
Npeople have signed up, it shows two buttons:
[ + Reservation ] and [ No ] - After
Npeople reserve a spot, the reservation button changes to:
[ + Waiting List ]
I think this will work best because "maybe" doesn't really make sense as a response in this case. What do you think?
-
Hi @PitaJ what about that?
N is max # of attendees
Case 1:
If less than N people have signed up, it shows 3 buttons: [ Yes ], [ No ], [Maybe]
⢠[ Yes ] goes to reservation list. First in first serve.
⢠[ No ] goes to the "No lis" for information only. Out of the purpose.
⢠[Maybe] goes to the âMaybe listâ. First in first serve.Case 2:
If N people have signed up, it shows 3 buttons: [ +Waiting List ], [ No ], [Maybe]
⢠[ +Waiting List ] goes to the âwaiting listâ. First in first serve.
⢠[ No ] goes to the "No lis" for information only. Out of the purpose.
⢠[Maybe] goes to the âMaybe listâ. First in first serve.Case 3:
If a confirmed attendee cancels his participation ( He clicks on [ No ]:
⢠The first one in the âWaiting Listâ will take the place. So, he goes to the âreservation listâ and he is removed from the âWaiting listâCase 4:
Nothing happen to the âMaybe listâ, unless someone changes his mind and decide to click on:
⢠[ No ] > despairs from the âMaybe listâ and goes to âNo listâ
⢠[ Yes ] > (if available) > goes to "reservation list". First in first serve.
⢠[ +Waiting List ] (if [Yes] is not available) > goes to the âwaiting listâ. First in first serve. -
@azeus okay so we thought up similar things. The only real difference is that you keep the maybe option.
I don't really think the maybe option makes sense when there's a limited number of slots for a certain event.
Does a person who responds with maybe get put on the reservation list or on the waiting list, assuming there are open slots? Does a person who responds maybe before another person responds yes get priority in the waiting list, or do people who respond with yes get priority over all maybes in the waiting list?
When you're just gauging attention or counting RSVPs, a response of yes, maybe, or no makes sense. But if you're providing a first come first serve opportunity, maybe doesn't make sense, in my opinion.
I'm open to having the third option but as of now I'm not convinced.
-
@PitaJ said in [nodebb-plugin-calendar] Fully featured calendar plugin for NodeBB - Testers needed:
Does a person who responds with maybe get put on the reservation list or on the waiting list, assuming there are open slots?
He's put on the "Maybe list" which is different from "Reservation list" and "Waiting list'. Actually there are 3 lists.
Does a person who responds maybe before another person responds yes get priority in the waiting list, or do people who respond with yes get priority over all maybes in the waiting list?
"Yes" (or reservation list) is the priority, and it's an automated action, when a sol is available the fits one in the "Waiting list" takes the place. The people in the "maybe list" stays in the 'maybe' list until they change their mind.
When you're just gauging attention or counting RSVPs, a response of yes, maybe, or no makes sense. But if you're providing a first come first serve opportunity, maybe doesn't make sense, in my opinion.
I'm open to having the third option but as of now I'm not convinced.
Your first proposal with only 2 options is fine for us
What we proposed is our nice to have, that fits 100% our need.Actually the whole idea about keeping the "Maybe", is that we know that our users don't know their planning in advance, and we are publishing our events mounts before the D date... Most of our users didn't confirm directly because they don't know if they are available... So if we have only 2 options "Yes" and "No", we think that most of them will click "No" or just does nothing... And then they will forget about the whole thing and never come back ^^ With the 'maybe' option, they keep event notifications and they keep tracking ....
-
Actually the whole idea about keeping the "Maybe", is that we know that our users don't know their planning in advance, and we are publishing our events mounts before the D date... Most of our users didn't confirm directly because they don't know if they are available... So if we have only 2 options "Yes" and "No", we think that most of them will click "No" or just does nothing... And then they will forget about the whole thing and never come back ^^ With the 'maybe' option, they keep event notifications and they keep tracking ....
So maybe doesn't really serve any purpose besides a way for users to be reminded of the event before it starts? Hmmm. Well at the moment, Maybe doesn't get any notifications except when the event starts. Perhaps change the three buttons to:
[ + Reservation ] [ Remind me ] [ No ]
And then when all reservations are full:
[ + Waiting list ] [ Remind me ] [ No ]
