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
F15451181: D17011.id40933.diff
Fri, Mar 28, 8:38 PM
F15442364: D17011.id.diff
Wed, Mar 26, 10:57 PM
F15442242: D17011.id40929.diff
Wed, Mar 26, 10:18 PM
F15438381: D17011.diff
Wed, Mar 26, 12:27 AM
F15408389: D17011.id40933.diff
Tue, Mar 18, 10:43 PM
F15395422: D17011.diff
Sun, Mar 16, 6:55 AM
F15334582: D17011.id40933.diff
Sat, Mar 8, 10:24 AM
F15334581: D17011.id40929.diff
Sat, Mar 8, 10:24 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.