Page MenuHomePhabricator

Remarkup CustomFields do not emit remarkup blocks when applied with ApplicationTransactions
Closed, ResolvedPublic

Description

I think it may be related yesterday's update. now we have a user upload a file, but the file he upload cannot be seen by others, like below:

I used my name to upload file in maniphest task as below:

undefined (274×928 px, 27 KB)

You can see file link in field. but when I open it with another user name:

undefined (222×1 px, 22 KB)

I think it is because file has not been inherits its paraent's permission. when I use the file link to access directly, it tells me below while I set the maniphest task visible to all users.
You do not have permission to view this object.
Users with the "Can View" capability:

darren.tao (Darren Tao) can take this action.
The user who uploaded a file can always view and edit it.
Files attached to objects are visible to users who can view those objects.

it blocked us, can you check asap? we did not hit such issue before only after yesterday's upgrade.

Event Timeline

taoqiping raised the priority of this task from to Needs Triage.
taoqiping updated the task description. (Show Details)
taoqiping added a project: Maniphest.
taoqiping added a subscriber: taoqiping.
chad added subscribers: epriestley, chad.

any findings, because it may block our process in some degree.

Oh, I think I figured this out by staring at it a bit more.

epriestley renamed this task from file attached cannot be download for other users to Remarkup CustomFields do not emit remarkup blocks when applied with ApplicationTransactions.Aug 21 2014, 11:20 PM

D10335 won't fix things retroactively, but will fix newly attached files.

You can likely fix things retroactively by editing the field where the file appears (just make any trivial change, and it will recognize that the file needs to be attached to the object).

Good thanks.
You guys response fast, and there isn't many tasks in such status. we can update manually.