translate5 has a lot of administrative configuration options.

Right now they are only settable at database level in the tables Zf_configuration and Zf_acl_rules (translate5 development team would love to get support for the development of a web-based administration wizard).

Zf_configuration

Please only change these settings, if you really know, what you do.

To people with basic programming knowledge, the table Zf_configuration and its contents should be self-explaining, the column description holds a brief description of the configuration parameter.

Language resource configuration

The following language resources can be configured for use in translate5:

• DeepL (as Plugin, only available for companies with a Support- and Development contract)
• Google
• Lucy
• Moses default
• MS Translator
• SDL LanguageCloud
• Globalese (not as part of Language Resources, but with a special integration)
• For SDL GroupShare please ask MittagQI

To integrate a language resources, query your translate5 DB for the following SQL query:

SELECT * FROM `Zf_configuration` WHERE `name` LIKE '%runtimeOptions.LanguageResources%'

This will give you the configuration values for all existing language resource integrations and some general configuration parameters for language resources.

How to configure each value is explained in the description column of the DB table for each value.

Help Page configuration

It is possible to show a help button in translate5. The button opens a pop up window with help content.

The displayed content must be provided as HTML-files to translate5 by the company using translate5.
At the moment no default help page content is provided by the installation.

The HTML-files that are provided as help content are loaded by AJAX and displayed in Popup Window in translate5.

When the configuration URL for the help files (details see below) is empty, the help buttons are not shown at all.

General help page for translate5

The configuration parameter in Zf_configuration for this is:

runtimeOptions.helpUrl

This URL can e. g. be set to the value

/help

With this URL the index.phtml view-script would be loaded from this location in translate5: 

/application/modules/default/views/scripts/help/index.phtml

(or from the client-specific overwrite-folder, if the view script does exists there)

Different help pages for each main section in translate5

If the every section in translate5 should have its own help content, a placeholder {0} can be provided in the configured URL.

This placeholder is replaced by one of the following values, corresponding to the translate5 sections:

editor, languageresources, taskoverview, useroverview

Example:

runtimeOptions.helpUrl = "/help/{0}"

When pressing the help button in the taskoverview the following relative URL would be loaded:

/help/taskoverview

Help page localization

The current locale of the authenticated user can also be passed to the URL via the optional placeholder "{1}". This fragment is replaced with the current users locale.

Also the whole URL can point to a completely different web page:

Example:

runtimeOptions.helpUrl = "http://www.example.com/translate5-help/?section={0}&language={1}"

Zf_acl_rules

Please only change these settings, if you really know, what you do.

Activate commenting of locked segments

To allow the user to comment locked segments, please execute the following sql-query on your translate5 database:

INSERT INTO `Zf_acl_rules` (`module`, `role`, `resource`, `right`) VALUES ('editor', 'basic', 'frontend', 'editorCommentsForLockedSegments');