Closed patrickmj closed 7 years ago
The change to make it work on the public side created this regression. On admin side, at least as global admin, site contexts don't exist, so the attempt to get it to work for public side fails because there's no site.
Thus, need to decide about different functionality between admin and public side. Should admin side follow a reintroduced global config, or should metadata browse just not be present on the admin side?
Alternative approach would be to have the admin side apply all the configs from all the sites, which seems kooky, but could be on the table.
Looks like I need to check admin or public side before looking up SiteSettings