You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 6.0.57 on production when creating a post to a group with members, the number of members previews as zero.
Go to a group with members that you are an admin for
Create a post
See how the panel says "All Members: 0"
After publishing the post, confirm with a group member that they did indeed receive a notification about the post.
When creating a group post the number of group members should default to the whole group and preview the correct number of members in the post creation panel.
An admin of a university-managed group also reported this issue.
The text was updated successfully, but these errors were encountered:
I was not able to reproduce the problem that you described. I tested with version 6.0.57 on production and the number of members shows as expected to me. Please see the attached video:
screen-20241212-092801.mp4
It takes time to load the group members and a spinning cursor is shown during that process. And after that the correct number is shown.
If you still observe an issue, could you please tell me the exact name of the group?
I will request to join in order to check if the problem is in the group.
@dobromirdobrev the issue is related to the group Gus with 574 members and the university-managed group "New Student Experiences" with more than 11,000 members. In Gus, I waited 3 minutes for the zero to change, and it did not.
I checked a couple other groups I administer that have under 100 members. The correct member number loaded right away in those cases.
In 6.0.57 on production when creating a post to a group with members, the number of members previews as zero.
When creating a group post the number of group members should default to the whole group and preview the correct number of members in the post creation panel.
An admin of a university-managed group also reported this issue.
The text was updated successfully, but these errors were encountered: