SymptomsStrings 'NOT TRANSLATED' exist on published site.
CauseLanguage pack is not fully translated or there was an old not fully translated version of language pack installed when issued site was created.
ResolutionCheck source language pack and translate all keys. After everything is translated properly compile new locale. Remove old locale from the Sitebuilder server. Install new fully translated locale.
If everything is fine with translation and new created sites do not have 'NOT TRANSLATED' strings it means that before new custom language pack installation there was old version of custom language pack installed and changes were not applied on already published sites. To apply changes on already created published sites following actions should be performed:
Copy all files from
If there are modules persist on the site also all files from
where SITEBUILDER_REPOSITORY_PATH - Path for Sitebuilder repository folder, as example, C:\Program Files\SWsoft\Plesk\SiteBuilder\Repository,
LOCALE - Locale identification letters, as en, ru, de...
SITES_DIRECTORY - Path for sites directory, as example, C:\Program Files\SWsoft\Plesk\SiteBuilder\Sites\d32ad73d-b3ea-4241-a456-ffcef01f11e3\
MODULE_NAME - the name of the module, as example Eshop/
After all these actions site must be fully republished.