I proposed two related patches in D25683 and D25685, both of them obsoleted by: D25687.

Probably OK now

Help welcome.

On a more meta level, Maniphest isn't well-suited to be an entry-form to be filled by a non-expert user; Nuance is/was intended for this use-case.

on the technical level, Herald can't block object creation - it runs after the fact, by the Daemons.

I don't believe in playing whack-a-mole on "could this be a password" but a use case I've been recently thinking of is "Do not allow task creation when task content/data is exactly the defaults provided by the Form used to create the task". Basically: You were supposed to fill in some stuff but you did not when creating your task.

This fix was super-interesting. Thanks again for the report.

After a small database inspection, it seems that uploading the picture causes:

(Oh sorry avivey, I have not noticed your priority action - I agree)

I do not (yet?) understand the use case of this task.

Indeed reported from a Wikimedia user about Wikimedia Phabricator.

In T15056#3210, @golyalpha wrote:

Another example of broken dark theme

A while ago I looked at this in downstream https://phabricator.wikimedia.org/T259329#9354946 (long version).
In short, rPce953ea4479052c7e671c8c75af6833252ebefd4 and rP657f3c380608abc0fc59088d979457f1d8826f06 are the culprits.

Yeah, in this one special place it doesn't matter; But that page already have a special body, so we can save even the extra click by putting the message right there...

OK I see. Indeed we should not put any similar button anywhere else.

But in Diffusion, that button is hidden behind a "Actions -> Manage" button, inside a screen that also has dozens of other admin actions. The clutter cost there is minimized.

I see. Maybe the root problem is that I'm in love with that Diffusion popup 🤔

In that case, we don't even need another button - just add a line to the "deleted message" that says something like "To completely remove the history from the database, contact your admin".

Premising the user already have an Delete Document button.

I feel that adding such a button would clutter the UI.
Users should generally "know" that in order to really delete things, they need to go to the admin, because they don't have the permissions anyway; And adding that just for the once-in-a-while that the admin needs this...

I mean, we can maybe have a "Delete" button that just shows the related CLI command, like I've seen around (Diffusion maybe)

I don't think we actually allow "deleting" from the web ui, only hiding it (in the sense that the data is not removed from the database).

This feature request could also be expanded to:

Since Subversion allows to checkout just a sub-directory,

Perhaps a single new sound is enough to change the world.

https://we.phorge.it/D25079#15506

I've better triaged my root problem.

Note that at least for Phame, http://phorge.localhost/J1 seems to always redirect to http://phorge.localhost/phame/post/view/1/blogpost/ instead of keeping the monogram in the URI.
So the baseURI is already wrong (not being http://phorge.localhost/ only) before concatenating the $ref (monogram and anchor).
As an ugly workardound, could probably make "Quote Comment" work by calling getObjectNamePrefix() in PhamePostRemarkupRule and LegalpadDocumentRemarkupRule and then use them in a preg_match to remove the monogram from the $ref but function is protected and... still ugly.

In addition, it seems only the owner can see their stuff here.

I ended up running this