It looks like the privacy on the main blog has been reset and is asking to sign in to access the homepage.
See related (resolved) ticket from two months ago: http://redmine.gc.cuny.edu/issues/1115
#1 Updated by Matt Gold over 10 years ago
- File Screen_Shot_2011-10-23_at_7.20.26_PM.png Screen_Shot_2011-10-23_at_7.20.26_PM.png added
- Category name set to WordPress (misc)
- Status changed from New to Assigned
- Assignee set to Boone Gorges
- Priority name changed from Normal to High
- Target version set to Not tracked
Just FYI, when I went to the dashboard, I saw the privacy settings shown in the attached image. We need to figure out how this happened.
#2 Updated by Boone Gorges over 10 years ago
We need to figure out how this happened.
Easier said than done. Probably a rogue plugin is changing blog_public meta values, but this is nearly impossible to track, especially for a one-time occurrence. The only plugin I know of that changes blog privacy settings on blogs other than the current blog is bp-groupblog. I've just done a brief audit and I can't see at a glance how even that plugin would be making this error, but it's possible.
A short-term fix, at least for the Commons main site, is to hardcode an exception to blog privacy rules, so that the main Commons blog cannot be set as anything but public (or, alternatively, it can never be hidden, even if the privacy level is set to private somehow). Obviously this is not a fix for the root of the problem, but it will at least prevent any repeats of the issue on the main site.
I'll continue to investigate to see if I can find any glaring issues that might have caused the problem in the first place, though I'm not all that hopeful.
#3 Updated by Boone Gorges over 10 years ago
- Status changed from Assigned to Resolved
- Target version changed from Not tracked to 1.2.5
I pushed the suggested changes in https://github.com/castiron/cac/commit/d9e1c15c20501015d1269f52b626b4c7c5b44abe
I still can't see what's going on more generally. I do see that a new blog was created on the 22nd with a privacy level of -2 (visibly only by blog members), which may be related, but that would mean that the Commons would have been hidden from non-logged-in users for a full day before the issue was reported, which I kinda doubt.
If the problem arises again (with the Commons or with any other blog), please let me know before switching the privacy settings back. That will give me more information for debugging. In the meantime, I'm going to mark this ticket as resolved, since it's as fixed as I can practically do at the moment.