Hi all,
We’re running Multiple Site Hosting (Concrete CMS 9.4.7) with two fully separate Sites (different Site Trees, different Canonical Domains, intentionally unrelated businesses), each with several Multilingual Sections.
Observation (see screenshots):
- Same Stack (ID 532, “Kontakt_Form_Offcanvas”), same locale (
nl_NL) — in both cases clearly labeled “Global” in the Dashboard breadcrumb. - Accessed via
rekers-garagen.de: the Stack shows the fully translated, correctly filled-out version. - Accessed via
rekers-beton.de: the Stack shows “This stack is not defined for Dutch (nl_NL): the default version will be used.” - On the frontend,
rekers-beton.deundernl_NLnonetheless renders the translation that was actually maintained underrekers-garagen.de— so the “not defined” Dashboard message doesn’t even match what the frontend actually shows.
The core of our concern: These areas are called “Global Areas” — we assume “global” means a Stack is a single, central resource treated consistently no matter which Site you access it from in the Dashboard. That’s also the whole point for us: we intentionally maintain content centrally and reuse it across multiple Sites.
However, the Dashboard view itself behaves inconsistently: same Stack, same locale, but a different displayed translation status depending on which Site’s URL you’re in the Dashboard through. This contradicts our understanding of “global,” and it took us a while to figure out what was actually happening — especially since the frontend consistently serves only the one translation (the one maintained under Site A) regardless of what the Dashboard reports.
Our questions for the community/core team:
-
Is it intended that the translation status of a Global Area Stack shown in the Dashboard depends on the entry-point Site, even though the Stack itself is shared across Sites and consistently served on the frontend? If not: should the Dashboard view instead always show the same (actually globally existing) translation status, regardless of which Site you’re accessing it from?
-
What happens if we click “Create localized stack version” from Site B, when Site A already has a translation for the same Stack/locale? As an editor on Site B, we have no visibility into the fact that a translation already exists on Site A — so we’d presumably end up creating a second, independent association without any awareness of Site A’s existing work. Specifically:
- Does the new Site B version stay isolated (with the frontend continuing to show the Site A version), or
- does the new association immediately take over resolution for both Sites — meaning a freshly created, possibly incomplete version on Site B could suddenly replace/override the currently working form on Site A as well?
Before trying this on our live installation, we’d like to understand how resolution works in this case, so we don’t accidentally break an already-working translation on the other Site.
Happy to share more details/screenshots if useful (we already have two side-by-side screenshots with identical Stack ID/URL structure). Thanks for any insight!
