Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
No, the user count is irrelevant. It checks the _notifications database for table rows of the group where the action is being performed. It then checks if the params column contains 1 of the notification parameters for that action set to yes. It then parses through those rows and validates they've permission to receive notifications for that group. It then takes the users output and loops through to send them notifications. I guess if your site has a limitation on emails sent (30 per hour?) and you're trying to send out 100 notifications at once it could stop sending emails for some users.Did you run tests with about 50 to 70 users and E-Mail notification ?
Pre-existing users don't benefit from the notification defaults. They must, 1 by 1, edit their notifications and set to receive them.Next idea : All users and groups already existed before I installed GJ 2.5. I am not shure, if users U1, U2 and U3 made any update on FE for notifications for G2.
Batch job for what? Batch processing has nothing to do with notifications.I tried to run the batchjob on BE in the group view. I had some difficulties to start them and I am not shure, if I did it the right way. Can you please explain, what exactly should be done, to run the batch job for a specific group (screenshot)?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Same as using Publish/Unpublish buttons. It lets you change some of the values of a category, group, or user on mass scale. For example I can change the category of 20 groups all at once.(by the way: what is the function of the batch job?).
You can, see CB > Config > Notifications > Defaults (also check Integrations for integration defaults). However, it does not apply to existing users. If a user joins a group for example those defaults will apply.Sorry but this design of migration (user has to set options for each group by lgging in and saving the options) is not very good. The site admin should be able to start with an empty _notifications table and fill it with default values for each user and notification type and general/category/group combination, that he configured to be changable by users.
Notifications must be opt in/out. Existing users must select what notifications they'd like to receive. New users joining the groups will of course have the default notifications as configured in backend applied to them.I run a site for a soccer club with 11 teams. Each team has it's own group. When the trainer of the team posts important message on the wall, it must sure, that each member of the group gets a notification. When
I can't ensure this, nobody will use the wall function on my site. The will stay at facebook !!!!
How it is now is how it will stay, sorry. GJ is completely open source and you're welcome to make whatever changes you want.So please try to find a solution to the big dilemma, this is very important for many users of group jive !!!!
Please Log in or Create an account to join the conversation.