Page MenuHomePhabricator

When a custom logo is configured but has a restrictive visibility policy, fall back to the default logo
ClosedPublic

Authored by epriestley on Dec 9 2016, 12:24 PM.
Tags
None
Referenced Files
F13201831: D17011.id40933.diff
Tue, May 14, 5:12 PM
F13191263: D17011.id40929.diff
Sat, May 11, 6:34 PM
F13185392: D17011.diff
Sat, May 11, 2:52 AM
Unknown Object (File)
Tue, May 7, 5:18 AM
Unknown Object (File)
Fri, May 3, 2:39 AM
Unknown Object (File)
Mon, Apr 29, 2:12 PM
Unknown Object (File)
Wed, Apr 24, 10:16 PM
Unknown Object (File)
Sun, Apr 21, 6:12 AM
Subscribers
None

Details

Summary

Fixes T11982. Currently, configuring a custom logo and then setting the policy restrictively locks off the whole install.

Test Plan
  • Configured ui.logo.
  • Searched for the file PHID in global search to find the underlying file.
  • Set the policy to something restrictive ("only me").
  • Purged cache (bin/cache purge --purge-all).
  • Restarted webserver to nuke APC.
  • Loaded a page as a different user.
  • Before change: policy exception while trying to load the logo.
  • After change: fallback to default logo.
  • Loaded page as user who can see the logo, got custom logo.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to When a custom logo is configured but has a restrictive visibility policy, fall back to the default logo.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Dec 9 2016, 3:20 PM
This revision was automatically updated to reflect the committed changes.