Question 1

How to fix "Invalid language identifier" error when clicking "Save to file" in Concrete CMS Translate Site Interface?

Accepted Answer

This bug affects Concrete CMS 9.x multisite installs (confirmed 9.4.7, still present in develop). "Save to file" resolves the site from the request host via `Section::getByLocale($localeCode)`, while the translation list/editor uses the site selected in the Dashboard site switcher (session-based `getActiveSiteForEditing()`). When the host-resolved site lacks the edited locale, the export fails with `Invalid language identifier`. Fix by patching `concrete/controllers/single_page/dashboard/system/multilingual/translate_interface.php`: (1) in `export_translations()`, change `Section::getByLocale($localeCode)` to `Section::getByLocale($localeCode, $this->getSite())`; (2) in `submit()` bulk export, change `Section::getList()` to `Section::getList($this->getSite())` (matching how Reload Strings already works). Without the fix, the export may also silently write the wrong site's translations if another host-resolved site happens to have that locale.

Question 2

How to fix 'Cannot access protected property' error in block templates after upgrading to Concrete CMS 9.5?

Accepted Answer

This is a known bug introduced in Concrete CMS 9.5 that breaks block templates using legacy variables like `$this->block` or `$this->controller`. The official fix will be released in version 9.5.1. If you need an immediate workaround, you can manually patch the core files: In `Concrete\Core\Block\View\BlockView::renderViewContents()`, change `$this->outputContent = $this->getTemplateService()->renderTemplate($this->template, $scopeItems, $this);` to `$this->outputContent = $this->getTemplateService()->renderTemplate($this->template, $scopeItems, $this->controller);` and in `Concrete\Core\Template\Service\TemplateService::renderPhpTemplate()`, change `$include = $include->bindTo($bindTo);` to `$include = $include->bindTo($bindTo, get_class($bindTo));`. Alternatively, update your templates to use injected variables like `$controller` or `$view` instead of `$this`.

Question 3

How to fix broken conversation subscription emails in Concrete CMS 9 (raw HTML anchor tag and error page link)?

Accepted Answer

Two separate fixes apply: 1) The raw anchor tag HTML appearing around the username was a core bug fixed by PR #12996 — update Concrete CMS to the latest 9.x release to get the patch. 2) The conversation link at the bottom of the email leading to an error page is caused by a missing or incorrect canonical URL configuration. Set the Canonical URL in Dashboard → System & Settings → Environment → URLs (or define `concrete.seo.canonical_url` in your config), then clear the cache via Dashboard → System & Settings → Optimization → Clear Cache.

Question 4

How do I fix the SMTP OpenSSL error after upgrading Concrete CMS to 9.5.0?

Accepted Answer

This is a regression in Concrete CMS 9.5.0 when using External SMTP Server; it is tracked as issue #12888 and fixed in an upcoming maintenance release. Upgrade Concrete CMS to the patched 9.5.x release as soon as it is available. As a temporary workaround, either downgrade the core to 9.4.8 after taking a full backup, or switch Dashboard → System & Settings → Email → SMTP Method from External SMTP Server to the default PHP mail() sending method if your server allows it. Retest using Test Settings or a form submission and check the logs afterward.

Concrete CMS

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects