Blog Sections Open
Avoiding 500 Errors When Disabling Languages in bLang
A troubleshooting note for multilingual Evolution CMS sites where bLang starts throwing 500 errors after language-state changes.
Multilingual sites often fail in subtle ways when language state is changed at the wrong layer. the discussion came from a bLang setup on Evolution CMS where disabling or reconfiguring languages led to 500 errors instead of a graceful fallback.
That kind of failure usually means the routing assumptions, host mapping, and enabled-language configuration no longer agree with each other.
What to watch
- Do not disable a language in storage if the routing layer still expects it to exist.
- Keep the configured domain or path mapping in sync with the active language list.
- Test default-language fallback rules after every bLang configuration change.
When bLang is working well, language switching feels invisible. When one part of the configuration drifts, the result can escalate into full server errors. That makes language-state consistency a real operational concern, not just a content setting.
Troubleshooting 403 Errors When a Resource Should Be Accessible
How to diagnose 403 access errors in Evolution CMS when a resource looks correctly published but still cannot be opened.
Why OnWebPageInit Can Break PHx and Built-In Modifiers
A parser troubleshooting note for projects where OnWebPageInit plugins interfere with PHx output or built-in Evolution CMS modifiers.