We have a multiple spaces that are normally viewed anonymously by our customers. However, 2 (and only 2) of these spaces are not viewable by anonymous users even though both the Global Permissions and Space Permissions are set to allow it. If the user clicks a link to get to those spaces, they are presented with a login page. If we set one of those spaces as the home page for the site, anonymous users are directed to the dashboard. We have verified that this is only an issue for anonymous users - licensed users can view the space.
We are using Scroll Versions to create and manage content for multiple versions of our product. We create content from a master space and publish it out to separate public spaces. (Scroll Versions is not active in the public spaces - only in the master.) Both of the spaces we are having issues with were published from a single version in the master space. We published an additional test space from this version and had the same result. Any ideas what could be causing this?
K15t was able to reproduce this on their end and is looking into it.
Sorry to anyone else who's experiencing this. We'll be working on fixing this bug,but in the meantime, here are the workaround steps:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do the pages in the published space have any sort of restrictions on them? If so, those restrictions will supersede the anonymous permissions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
They do not. We had this space available before, but when we republished, it was no longer viewable. We don't have any restrictions on any of the pages, and I double-checked to make sure that was still true.
Oddly, our administrator restarted the server and it started working. This was the second restart - we'd restarted it shortly after we noticed the issue and it didn't do anything, but the second time fixed it. It's no longer blocking our customers, but I'd still love to figure out what happened in case it happens again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am not 100% if this relates to your case but please be aware I have stumbled about a bug which is related - the Atlassian team is already investigating
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Note that Scroll Versions is not activated in these public spaces - only in the master space.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.