There are a fair number of bells and whistles users can configure for this module. We should update the README.md with robust documentation to make it as easy as possible for users to install and use the module.

Comments

JayDarnell created an issue. See original summary.

jaydarnell’s picture

Issue summary: View changes

jaydarnell’s picture

Status: Active » Needs review
artatac’s picture

Thanks so much. I will work through the instructions and report back

jaydarnell’s picture

You're welcome artatac. I'll also make some time to add a guide here on drupal.org later this week. It would probably be helpful to see this same documentation coupled with some screenshots for added guidance.

artatac’s picture

great work thanks. I have it running, here is some feedback:
Site wide announcements work well, trying to understand what 'immediate' means, is it that as soon as the announcement is created it gets sent or as soon as cron next runs?
I could not understand why the feature to omit certain group content was not available until I went to /admin/group/types/manage/section/permissions and realised that this was NOT turned on my default for user 1. so now I know but it may trip up others
I can see why the default is that users have to opt in to these mails but in our case we ask all intranet member to use this. As it is now if I set up a new user > add them to say 3 groups. I then have to remember each time to then go to their profile (again) and alter group subscriptions from disabled to immediate. It would be great if there was the option to default it to say daily. even if you then remind the user they have control and can alter it back. I presume at its most basic there is a line of code in the module that says "default for users new groups = disabled" If you could point me to that I could make a simple change that would work better for our setup.
if you thought is has wider value then maybe you expose the default (disabled) at /admin/config/content/group_subscription and allow it to be changed there - just a thought.
I set most test users to 'immediate' but one to receive daily digest. The time has gone past when I was expecting this to be sent but it may just require some extra patience on my part!
Thanks again for the hard work you have put into this module

Webbeh’s picture

You're welcome artatac. I'll also make some time to add a guide here on drupal.org later this week. It would probably be helpful to see this same documentation coupled with some screenshots for added guidance.

Kickstarted the d.org guide page: https://www.drupal.org/docs/contributed-modules/group-subscription

I suppose this leads to a bigger discussion on which content currently in the README still belongs there, and which can be moved to the Guide as more hands-on/intensive docs.

jaydarnell’s picture

Thank you so very much for your feedback artatac! I am thrilled to hear you have it working and would like to respond to your feedback below:

Site wide announcements work well, trying to understand what 'immediate' means, is it that as soon as the announcement is created it gets sent or as soon as cron next runs?

You bring up a very good point. Yes, immediate subs are processed on the next cron run. I initially called this "immediate" based purely on the nomenclature we were using for one of our projects. I created this contrib module to replace a custom module and "immediate" and "daily" were the terms in place our users were accustomed to seeing. That being said, the term is slightly misleading as the "immediate" subscriptions are processed on the next cron run (and the time between runs is variable based on how you set up your server). I should either change the terminology OR be sure this is clearly documented in the interface.

I could not understand why the feature to omit certain group content was not available until I went to /admin/group/types/manage/section/permissions and realised that this was NOT turned on my default for user 1. so now I know but it may trip up others

This is certainly easy to miss, needs to be clearly documented, and could benefit from having a default set.

I can see why the default is that users have to opt in to these mails but in our case we ask all intranet member to use this. As it is now if I set up a new user > add them to say 3 groups. I then have to remember each time to then go to their profile (again) and alter group subscriptions from disabled to immediate. It would be great if there was the option to default it to say daily. even if you then remind the user they have control and can alter it back. I presume at its most basic there is a line of code in the module that says "default for users new groups = disabled" If you could point me to that I could make a simple change that would work better for our setup.

This is also great feedback and relates to an issue I had previously created to provide a mechanism for admins to apply group subscription settings in bulk. I've modified and updated the issue here: https://www.drupal.org/project/group_subscription/issues/3150014 (lets continue this conversation there - I'd welcome more of your feedback on this issue to help me craft a flexible solution)

I set most test users to 'immediate' but one to receive daily digest. The time has gone past when I was expecting this to be sent but it may just require some extra patience on my part!

Did the immediate subs come through? Did the Daily sub? Are you running with an automatic cron process or testing with a manual one (and what hour is your daily processing set to in the module settings)

Thanks again for the hard work you have put into this module

Thank you for giving the module a try and for your very helpful feedback.

jaydarnell’s picture

Kickstarted the d.org guide page: https://www.drupal.org/docs/contributed-modules/group-subscription

I suppose this leads to a bigger discussion on which content currently in the README still belongs there, and which can be moved to the Guide as more hands-on/intensive docs.

Thank you for creating this stub! Time got away from me last week and I've yet to start on this.

artatac’s picture

What “immediate” means
Maybe just an *”this is dependent on site (corn) settings and could be a few hours - check with your admin”

What I have been doing which works ok is forcing a manual cron run

First thought would be to use the replacement word “ASAP”

Trouble with immediate is that unless it appears within 40 seconds one assumes it isn’t working!!

jaydarnell’s picture

artatac, I've created a couple new issues for the items identified above:

Clarify "Immediate" Language
https://www.drupal.org/project/group_subscription/issues/3209522

Document permissions for omitting group content from subs
https://www.drupal.org/project/group_subscription/issues/3209525

jaydarnell’s picture

Version: 8.x-1.x-dev » 2.0.x-dev
Status: Needs review » Fixed
jaydarnell’s picture

Status: Fixed » Closed (fixed)