From InClickAdServer


Supported Languages

Currently, the inClick ad server supports the following languages.

  • Arabic
  • English
  • German
  • Russian

If you would like to assist us in translating the ad server to another language, or have a language that is not currently listed above, please open a support ticket here:

 Open New Support Ticket

We will provide you the English version of files to be translated by you.

Enabling Language Selection

To enable language selection do the following:

  1. Ensure you are using inClick version 4.1.002 or newer
  2. Login to your ad server as the Administrator
  3. Go to System Setup and scroll down to Languages and click the 'Edit' link.
  4. Enable whichever languages you would like to use and click 'Save System Setup'
  5. Log out
  6. Check the header for the language selector. If it is present you are all set. If it is not present, go to the next step.
  7. If the language selector is not available it means you are using an older version of the:

file. The header.html file is not overwritten on upgrade to allow customization. To add the language selector insert this code into the appropriate part of your header:

If you have any questions or problems do not hesitate to contact inClick support for further assistance.

Language Customization

Do not simply modify the files in [INCLICK_HOME_DIR]/lang/[language]/ as these files will be overwritten upon your next upgrade!

You can provide your own text for any part of the system. To do this, do the following:

  1. Determine which file the text you would like to replace is in. You can either look at the language files directly in:

    and find the text you would like to change.

    Alternatively you can enable the language debug mode by adding this:

    to the file:

    This will add a 'debug mode' link next to the language selector. When selected this displays the text string that is used for any given section shown by the system.
  2. Whichever method you choose, your goal is to get the string code which will be of the form [section].[type]..., an example would be:
  3. Once you have the string code(s) you would like to replace, then for each language you want to use you would:
    1. Check if the custom file exists for that language. If this is your first customization it likely does not, so you will want to create the file:

      In the example above the file to be created would be:

      The file MUST be named according to the first part of the text string, and will be one of: common.php, advertiser.php, publisher.php, admin.php, emails.php.

    2. Once the file is created, then you would add your own string of the form:

      or to override the example you would have:

    3. Repeat the above process for as many text strings and languages as you would like to replace.

Accessing Current Language

There are many instances where you would like to know what language the user has set so that custom pages, the header, or other parts of the system respect their choice. This information is available two ways:

  • Session variable named 'language':
  • Cookie named 'language':
  • The value stored in these will be the short string for the language, ie. 'english', 'german', 'russian'...

Terms of Service Customization

Currently, the terms of service is only in English. If you would like to provide alternate versions for your users you will need to:

  1. Translate or create your own Terms of Service for each language you would like to support.
  2. Update the Terms of Service links to point to a custom page. To do this, add the following to [INCLICK_HOME_DIR]/globals/globals_custom.php:

These should be full URLs to a page that lists the available terms of service by language. Alternatively, if you would like to use the user's current language then use method described in Accessing Current Language. Then you can simply display the appropriate Terms of Service for the user's selected language.

Custom Filter Language Support (Version == 4.1.006-1)

Previous to this version, the Custom Filter System supported English text only. As of 4.1.006-1, the Custom Filter System was updated to support multilingual deployments. To support this, the user must modify/create custom language files as listed below. Each supported language must have these files defined or the section will appear in English.

The examples below all override the language settings for filter index 1 but can be changed to any of the potential indices of 1-3.

Advertiser Updates

File: /lang/custom/[language_code]/advertiser.php

$lang[''] = 'Target Filter(s)';
$lang['advertiser.labels.custom_filters.1.available'] = 'Available Filters';
$lang['advertiser.labels.custom_filters.1.selected'] = 'Selected Filters';
$lang['advertiser.notes.custom_filters.1'] = 'These are the notes shown to the advertiser for the filter.';
$lang['advertiser.values.custom_filters.1.target_any'] = 'Target Any Filter';
$lang['advertiser.values.custom_filters.1.target_specific'] = 'Target Specific Filter';

Publisher Updates

File: /lang/custom/[language_code]/publisher.php

$lang['publisher.notes.custom_filters.1'] = 'These are the notes shown to the publisher for the filter.';

Common Updates

File: /lang/custom/[language_code]/common.php

$lang['common.titles.custom_filters.1'] = 'Filter Title';
$lang['common.labels.custom_filters.1.code_XXXX'] = 'Filter Text for code XXXX';

XXXX is the filter_code value for each record.