Article ID: 5544, created on Aug 13, 2008, last review on Apr 27, 2014

  • Applies to:
  • Sitebuilder 4.x for Windows


Strings 'NOT TRANSLATED' exist on published site.


Language pack is not fully translated or there was an old not fully translated version of language pack installed  when issued site was created.


 Check 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.

fad6dc0c8e983c17ae70a51ac7952cd0 2a62cbceb986d1b8f45bcd3ff4cb29a5 45e8c8798afdb3e279a2f84bd498d19e 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF