i am one of the admins in our phabricator instance:
but i don't have the ability to edit or delete off-topic ponder questions?
shadowhand | |
Aug 11 2014, 5:46 AM |
F188799: Screen_Shot_2014-08-11_at_0.44.45.png | |
Aug 11 2014, 5:46 AM |
F188796: Screen_Shot_2014-08-11_at_0.44.14.png | |
Aug 11 2014, 5:46 AM |
i am one of the admins in our phabricator instance:
but i don't have the ability to edit or delete off-topic ponder questions?
This is currently intended. Administrators have very little power, see:
https://secure.phabricator.com/book/phabricator/article/users/#administrators
If a user files a task and sets edit permissions restrictively, you can't close it either.
In the general case, you can use bin/policy unlock XYZ to unlock an object, and bin/remove destroy XYZ to totally destroy an object, regardless of policies.
I think we'll probably make Ponder default policies more open at some point. Part of the issue is that Ponder doesn't explicitly expose policies.
The recommendation of using bin/policy does not work:
$ bin/policy unlock Q4 Unlocking: Q4: how to use the function of 'phlux' in phabricator View policy is not mutable. Edit policy is not mutable. Object has no mutable policies. Try unlocking parent/container object instead. For example, to gain access to a commit, unlock the repository it belongs to. $ bin/remove destroy Q4 Usage Exception: Object "Q4" can not be destroyed (it does not implement PhabricatorDestructibleInterface).
Any other recommendations?
Oh, haha.
Ponder is really behind the times.
You should still be able to bin/remove destroy it, or you can spelunk around in the DB.
$ bin/remove destroy Q4 IMPORTANT: OBJECTS WILL BE PERMANENTLY DESTROYED! There is no way to undo this operation or ever retrieve this data. These 1 object(s) will be completely destroyed forever: - Q4 (PonderQuestion) Are you absolutely certain you want to destroy these 1 object(s)? [y/N] y Destroying objects... Destroying PonderQuestion Q4... Permanently destroyed 1 object(s).
I'm going to close this under the "No Prototype Requests" rule, and since modern policy support would certainly be part of T3578 if we move forward with that.