Open xet7 opened 6 years ago
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.
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
From @garrison on April 1, 2016 21:9
Sounds great to me.
I visited the issue list to make totally same proposition. So let me support @garrison on this one.
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