Skip to content

Don't rely on project privacy level for sitemap and robots.txt #6196

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

stsewd
Copy link
Member

@stsewd stsewd commented Sep 18, 2019

Use the default version privacy level instead

Ref #2663

Use the default version privacy level instead
@stsewd stsewd requested a review from a team September 23, 2019 15:36
@agjohnson
Copy link
Contributor

I think this probably makes sense, though maybe something we want to figure out in design decision first. I'll block on #6194 for now, as there is some conversation there.

The main problem I have with this currently is that project default privacy level is overloaded with function now and we aren't communicating it's usage to users sufficiently yet.

@agjohnson agjohnson added the Status: blocked Issue is blocked on another issue label Sep 24, 2019
@humitos
Copy link
Member

humitos commented Sep 30, 2019

Just want to mention that this may makes sense only in Community. Corporate should probably return 404 when it's a private.

@stsewd
Copy link
Member Author

stsewd commented Apr 16, 2020

This was already done in #6798

@stsewd stsewd closed this Apr 16, 2020
@stsewd stsewd deleted the dont-rely-on-project-privacy-level branch April 16, 2020 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: blocked Issue is blocked on another issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants