Limit what user data counts as 'safe'
Add Profiles.View check to user/summary endpoint
UserModel GetSummary should return corrected PhotoUrls
Add Gdn_Request->AssetRoot() to decouple the root of static assets from the root of dispatched requests.
Add Gdn_Request->UrlDomain().

This is a convenience function for conditionally getting the current domain in various formats.
Change Asset() and SmartAsset() to use Gdn_Request->AssetRoot().
Fix bug in the Emoji class where Url() was called instead of Asset().
Fix the translation of “Locale”.
Revert "Fix the translation of “Locale”."

This reverts commit 521e5b5445014368f9ff1721899280d5a670b10f.
Fix the translation of “Locale”.
Merge pull request #2163 from vanilla/hotfix/summary-leak

Restricts guest access to user data & fixes photo URLs for WordPress
Merge pull request #2167 from vanilla/hotfix/locale-name-fix

Change the translation of "Locale".
Merge branch 'hotfix/locale-name-fix' into feature/decouple-request-root
Merge branch 'feature/decouple-request-root' of github.com:vanilla/vanilla into stage
Add a display as option of “Heading” to categories.

The Vanilla.Categories.DoHeadings has the effect of rendering all categories of depth 1 to be headings. This change paves the way to have sub-categories also display as non-clickable headings.

Note that this pull request doesn’t update any views at this time so additional view work will have to be done in a future pull request.
Link to # in the breadcrumbs when a breadcrumb doesn’t have a url.
Add the $includeHeadings parameter to CategoryModel::GetAncestors() which can be used to exclude heading categories.
Add the $IncludeParent parameter to CategoryModel->GetSubtree().
Don’t include the current category in the “Categories” key of the result.

This change adds some consistency to our api. When you are viewing the root then all of the categories are shown, but not the root category. The same should be true when viewing an individual category because you really don’t want to display THAT category in any list whether it be a category list, a subtree or what have you.

This change does add some risk as it’s changing an api we’ve relied on for a long time. I’m hoping that these changes make any regression bugs worth it though.
Don’t use do headings to adjust a category’s depth.

I’m fairly certain that due to making the categories api more consistent then this tweak is no longer necessary.