Keep translations attached to the intended KB article so a language update does not accidentally create another page or replace the main version. Use the language fields supported by your installation.

Confirm content permissions

Use a dedicated content connection with a Write ceiling, the required content area and staff permissions. The separate read-only override must permit the intended write. The company needs an active Support Manager plugin, and the bound active staff member’s group needs its Knowledge Base permission. A connection limited to selected clients cannot operate on the shared knowledge base.

Blesta stores language versions on one Support Manager article. Its tools use language codes such as en_us, with the connection’s default language context used when a language is omitted. Confirm the intended installed language and company rather than borrowing a code from another system.

Add a language to the existing article

1. Read the existing article and inspect its content entries and language values.
2. Prepare and review the new language’s title and body.
3. Ask the assistant to use Edit a knowledge base article with the existing article ID, the target language, title and body.
4. Keep the article’s access and categories unchanged unless those changes are separately intended.
5. Read the same article back and inspect the new language entry and the earlier language versions.

Use the update operation to add this language to the existing article. Add a knowledge base article creates another article and is not a translation-linking command; these Blesta tools do not expose a translation_of field.

Preserve format and earlier versions

Check the language entry’s content_type. Keep HTML as HTML and plain text as text, or explicitly prepare and review a format conversion. An edit merges supplied language text with that entry’s current values; still provide and verify the complete intended title and body when adding a new language.

Check the final language and access

Read the article after the change and compare the requested language text, earlier versions, categories and audience. Language editing does not authorise broader publication. Review the native page in the intended language too; a saved entry is not proof that a language selector or template displays it as expected.

If an error occurs, read the existing article and language entries before retrying. Do not delete the main article to remove a mistaken translation attempt, because that would affect more than the one language version.

See the PD MCP Hub Blesta guide for related tasks, or explore PD MCP Hub.