Page MenuHomePhabricator

Don't require edit capability on the Favorites application to edit personal menu items
ClosedPublic

Authored by epriestley on Jan 19 2017, 7:11 PM.
Tags
None
Referenced Files
F12814000: D17228.id41437.diff
Thu, Mar 28, 1:39 AM
Unknown Object (File)
Wed, Mar 20, 4:42 PM
Unknown Object (File)
Mon, Mar 4, 7:07 AM
Unknown Object (File)
Feb 13 2024, 10:02 AM
Unknown Object (File)
Feb 4 2024, 4:49 PM
Unknown Object (File)
Feb 3 2024, 2:07 PM
Unknown Object (File)
Jan 24 2024, 1:27 AM
Unknown Object (File)
Jan 9 2024, 10:23 AM
Subscribers

Details

Summary

Ref T11096. Currently, editing ProfileMenuItemConfigurations always requires that you can edit the corresponding object.

This is correct for global items (for example: you can't change the global menu for a project unless you can edit the project) but not for personal items.

For personal items, only require that the user can edit the customPHID object. Today, this is always their own profile.

Test Plan

As a non-admin, edited personal menu items.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

How should we have caught this? Non-admin testing?

This revision is now accepted and ready to land.Jan 19 2017, 7:13 PM

Yeah, non-admins editing their own items.

(I tested a bit as as a non-admin but didn't try to customize the menu, and customized the menu only as an admin.)

This revision was automatically updated to reflect the committed changes.

Is there any way that getCustomPHID would return false/null when it's a non-admin editing favorites?

I got this report, which seems like the same issue: https://phabricator.wikimedia.org/T156360

Haven't seen other reports, not sure how to reproduce that.

AH ok I can reproduce, will file something