Page MenuHomePhabricator

Changing permissions of a moved wiki page results in: A moved document can not be deleted.
Closed, ResolvedPublic

Description

I created a wiki page, limited the permissions to one group, moved it. Now, when accessing the old URL, I see This document has been moved to /w/…. I click Edit Document and change permissions to All Users. Upon saving changes A moved document can not be deleted. is displayed in red.

What I would actually like to do is clean up the old wiki page in a way such that the URL can be used anew when someone deems it necessary, without seeing the old content (or title) and without being hindered by any permission issues.

Event Timeline

devurandom raised the priority of this task from to Needs Triage.
devurandom updated the task description. (Show Details)
devurandom added a project: Phriction.
devurandom added a subscriber: devurandom.
btrahan added a subscriber: btrahan.

One way to delete a wiki document is to clear the document body and hit "save".

This task and T7328 are the same confusion over this feature. I'll try to clarify the error message flow around this a bit.

That said, there's always going to be the "this page was deleted" UI there until someone else creates something. For any given page, a complete history is always there. Otherwise though, it should behave like new, etc.

I think tailoring the error message is sufficient. Letting users edit the title of deleted documents feels weird / surprising.

Is it possible to delete the title (and permissions) along with the rest of the document? I currently have a stale page at /w/generic-url with the title "Super Secret Dev Team's Super Secret Wiki Page" and permissions set to that dev team. I moved the page to /w/super-secret-dev-team/generic-url, but now I am stuck with the redirect page preventing reuse of /w/generic-url.

You should visit /w/generic-url, specify some content along with the other edits you seek, hit save, then delete the document again.

...in theory this should now be clear to you from rP0a0ac1142953.

/w/generic-url is private to that project. I cannot even view it without cheating myself into the project by force of my admin powers.

I'm not sure how you made all these other edits then?

I added myself to that project. I cannot expect that from everyone on my site.

Please also note that in my reports I try to give the most simple steps for reproduction. I might report an issue which includes steps done by someone else, and still write "I" for simplicity.

I added myself to that project. I cannot expect that from everyone on my site.

Please also note that in my reports I try to give the most simple steps for reproduction. I might report an issue which includes steps done by someone else, and still write "I" for simplicity.

It would be best if you were as accurate as possible first, and then optionally if you want to figure out more simple reproduction steps that sounds great. This is important so we don't lose the context of what's happening, or in this case, end up with "reproduction steps" that actually make no sense based on how the system works.

Phabricator isn't a system intended for use with "bad actors" - e.g. you might need to train the users of your system how to use a wiki if they aren't familiar with such things. We do provide policy controls - e.g. you could make a page /w/mystuff/ and restrict it to just you and have lots of fun without anyone messing things up under there - but by default users are going to get their druthers on a vanilla Phabricator installation and have as much power as they can imagine.

So, I think the real scenario here is

  • A makes a page with view policy just to them
  • A deletes (or moves) the page
    • Note that this could be super secret stuff and the wiki keeps its history so changing policy as a side effect of delete (or move) is bad?
  • B comes to the old page and can't use it
    • but they get a notice that A can use it
    • so they go ask A to fix it
    • A can say "sorry man, that's where I kept all the secret stuff so that gone" or help them out, depending.

...this is how Phabricator works basically - individuals have lots of power and are expected to work well with the other individuals involved.

Its potentially likely you don't want a wiki as a solution? This is how it works however.