Skip to content
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

Support fully private blogs #13

Open
xet7 opened this issue Mar 8, 2018 · 4 comments
Open

Support fully private blogs #13

xet7 opened this issue Mar 8, 2018 · 4 comments

Comments

@xet7
Copy link
Member

xet7 commented Mar 8, 2018

From @garrison on February 13, 2016 0:38

As discussed on IRC on 2015-02-10, it would be great if wordpress-sandstorm supported private blogs. Of course, a blog is private until its public link is shared, but once that link is shared it is difficult to revoke. It would be great instead to be able to disable the public site entirely.

Copied from original issue: dwrensha/wordpress-sandstorm#17

@xet7
Copy link
Member Author

xet7 commented Mar 8, 2018

From @garrison on April 1, 2016 4:7

Quick update: A collaborator clicked the "Regenerate Public Site" button on our private blog, so now we have a public site even though we don't want one, and there is currently no way to undo this. I also believe the URL is being leaked any time we access the "public" site over an open internet connection, since the full URL can be gained by eavesdropping on DNS lookups.

@xet7
Copy link
Member Author

xet7 commented Mar 8, 2018

From @paulproteus on April 1, 2016 5:21

Perhaps one fix for this would be to, next the

"Regenerate public site"

button, add a smaller link that says, "Disable publishing", and when you
click it, you get a Javascript prompt that says, "This will remove all
content from your public site. To view the blog, users will have to log in
to Sandstorm. OK?"

Then from the WordPress side, one would "just" rm -rf /var/www

What do you think of that? & David Renshaw too

@xet7
Copy link
Member Author

xet7 commented Mar 8, 2018

From @garrison on April 1, 2016 21:9

Sounds great to me.

@searoso
Copy link

searoso commented Jan 3, 2019

I visited the issue list to make totally same proposition. So let me support @garrison on this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants