We are looking at as a priority issue.

We have already removed all non-members from watching private sites. We are working on a permanent solution.

However, even if non-members were subscribed to private sites, they did not receive any activities.

We have discovered minor issues related to private categories on public sites and listing activities for non-member watchers. We will be addressing these issues later today.

Thank you. That final comment regarding private categories is one that is addressing us as well because we have public pages available for our clients and private pages for employees.

We did a code review and after all there was no real problem with private content. Although unauthorized users might be listed on pages or categories they do not have permission to access, they are not getting any notifications.

Now, when a member is removed from a private site, all activity subscriptions are also deleted.

Now, when a member is removed from a private site, all activity subscriptions are also deleted.

Four users of our site are still watching every page, even though they have been deleted as members.
Miss Jennie
Matt McGwire
Ayana Miki
ji young

Additionally, there is a bug that prevents me from changing the site from "closed" with private categories to fully "private". Every time I make the attempt it just says "saving changes"… forever. So I'm not able to make the site private to see if it drops the previous members as watchers.

Also, there is a new issue with watching. Two new staffers, one employee and one intern that just joined us have been automatically made watchers of the entire site.

Removing a member on a non-private site does not remove them from watchers.

Indeed there is a problem with switching access policy to "private" for some sites. We are working on it now.

New members watch the site they join by default. It was always the way it worked, despite it did not work in some cases due to a bug we have discovered (and fixed) recently.

We will keep this issue updated.

We have fixed issue with switching access policy by moving tasks related to search into backend queue.

New members watch the site they join by default. It was always the way it worked, despite it did not work in some cases due to a bug we have discovered (and fixed) recently.

Interesting. It was not perceived as a bug from our view, but rather an "opt in" choice. So now, the first thing we have to do with every new Intern or Employee is tell them to go and unwatch the site. Seems a bit spammy to me.. they join a site and immediately begin to get in email notifications that they did not opt in to receive. In our case, they get tons of emails daily.

We are still unable to remove ex members from the our watch list. I understand that they don't get notified, but we still see them on lists that we would prefer not display user names of former members. It is very annoying and confuses our staff as they are asking who is such and such and why are they watching my job…

I just realized this says "completed". This is still an issue for us. I don't understand how it is done when we still have a problem. I can set the site to private and that removes the previous members as watchers, but as soon as I put it back to the way we need it (closed) all those members re-appear.

To illustrate how serious this is for my seniors, they have asked me to look into getting someone in my staff working with Word Press sites to switch over from Wikidot sites to Word Press.