Skip to content

[6.x] Multisite improvements - entry vs global - #15191

Merged
jasonvarga merged 9 commits into
6.xfrom
multisite-improvements-entry-vs-global
Aug 14, 2026
Merged

[6.x] Multisite improvements - entry vs global#15191
jasonvarga merged 9 commits into
6.xfrom
multisite-improvements-entry-vs-global

Conversation

@jaygeorge

Copy link
Copy Markdown
Contributor

Description of the Problem

The global localization selector is often confused with a language selector, or the difference between the global site selection and page localization is confused.

I've experienced this myself and it's also mentioned here.

I think we can fix this with a few careful changes

What this PR Does

  • Adds the word "Site" to the global localization selector so it's not confused with a language selector
  • For the entry localization, make the language simpler: "Current Localization" -> "Working In"
  • Add a localization icon to the entry localization too, so it's clear it's somewhat related to the site selector in the header

Few Localizations UI - Before

2026-08-13 at 17 38 12@2x

Few Localizations UI - After

2026-08-13 at 18 28 37@2x

Many Localizations UI - Before

2026-08-13 at 17 39 17@2x

Many Localizations UI - After

2026-08-13 at 18 28 54@2x

How to Reproduce

  1. Go to a collection where localization is enabled e.g. enable it with /cp/collections/blog/edit
  2. Try it with more than three localizations enabled, which triggers a combobox, and also two localizations enabled, which is a different UI

@jasonvarga
jasonvarga enabled auto-merge (squash) August 14, 2026 16:54
@jasonvarga
jasonvarga merged commit 57074c8 into 6.x Aug 14, 2026
64 checks passed
@jasonvarga
jasonvarga deleted the multisite-improvements-entry-vs-global branch August 14, 2026 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants