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
Can read a private post (draft) in edit mode #255
Comments
Thanks for the report! Depending on your configuration, this might be correct behavior -- drafts are meant to be shareable on public instances. But we'll want to make sure visibility is consistent between the What is the visibility setting of your blog (Unlisted, Private, etc.)? And what is the |
The above behaviour is from an |
Hmm, that's pretty odd. You should see the same behavior either way, if you're just talking about the blog setting (as opposed to the instance setting). Is the |
in the config file |
Gotcha, thanks. So from my understanding, the primary things to address here are:
Out of curiosity, is there something about how you use WriteFreely that requires completely private / unshareable drafts? |
I use it for notes in general (drafts for private, and published for public). But I assume that's not the target audience either way. |
Ah, makes sense. Yeah, we plan to support that exact use case another way, so we can keep WriteFreely focused on public content. But that's great to know! |
Describe the bug
If I'm not logged in, but I know the url of a draft, I can see it's content
Steps to reproduce (if necessary)
Steps to reproduce the behavior:
https:://site.com/d/random-id
)https:://site.com/d/random-id
) and it shows a 404/edit/
to the copied url (https:://site.com/d/random-id/edit
) and it shows you the edit page. You can't actually edit, but now you can see the content.Expected behavior
What should've happened?
I would expect a 404 or some other error
Application configuration
Version or last commit:
writefreely -v
only prints outWriteFreely
but in my package manager it says I have version0.11.2-2
installedThe text was updated successfully, but these errors were encountered: