2 Step By Step Installation Guide | Translator Revolution PRO

Step by step installation guide - Translator Revolution PRO

Provides "step by step" documentation for the installation process.

Installation guide

  1. Introduction
  2. The original webpage
  3. Overview of the folder structure
  4. Copying the translator's files
  5. Selecting a spot to place the translator
  6. Placing the translator's code
  7. Changing the translator's folder location
  8. Modifying the default settings
  9. Selecting areas to translate and to exclude from translation
  10. Adjusting the layout
  11. Watch the video

1. Introduction

This "step by step" guide will show how to install the Translator Revolution PRO on a sample webpage.

All the sample files used for the guide are in the /help/project/ folder.

2. The original webpage

  • The original webpage looks like this (/help/project/step_2/webpage.php):
  • And its XHTML looks like this (/help/project/step_2/webpage.php):

3. Overview of the folder structure

  • The folder structure (/help/project/step_2/):

4. Copying the translator's files

  • On the package's folder structure, identify the translator's main folder:
  • Copy and paste the translator folder to the website's root folder (/help/project/step_4/):

5. Selecting a spot to place the translator

  • Using a XHTML DOM inspector (which is built in Chrome and in Internet Explorer 9, also can download the Firebug plugin for Firefox too), select an element which is close to the desired spot, for instance, the "The first car" header:
  • Identify the HTML code, <h2>The first car</h2>:
  • Find the HTML code (/help/project/step_4/webpage.php):

6. Placing the translator's code

  • The SurStudio Translate API requires an API Key. In order to get one, follow the steps:
    • Get the Item Purchase Code.
      • Go to the downloads' page.
      • Download the license certificate.
    • Go to http://codecanyon.net/user/SurStudio/
    • On the lower right side there's the following email form:
    • Send a message with the purchase info. The following sample message could be used as template (highlighted is the required info):

      Hello there,

      here I'm attaching the required info to get a key to use the translation service.

      Name: John Doe
      Email: john.doe@emaildomain.com
      Product: Ajax Translator Revolution Wordpress Plugin
      Item Purchase Code: f4b3ae24-d23f-42a3-80a6-41c37ced6961
      Website's base URL(s): mydomain.com, sales.mydomain.com, mysubdomain.mydomain.com
      Website's source language: English


    • An email will be sent back shortly, with the API Key.
  • Place the API Key in the /translator/config.class.php file, line number 88:

    api_key = A65A1D6789C4262632B38305AE4975A61C054A01
  • Add the initialization lines in the previously selected spot:

    <!-- translator begins -->
    <?php
    require_once dirname(__FILE__) . '/translator/main.class.php';
    TranslatorManager::initialize();
    ?>
    <!-- translator ends -->
  • Before (/help/project/step_4/webpage.php):
  • After (/help/project/step_6/webpage.php):
  • Open on the browser:
  • Notice the line:

    require_once dirname(__FILE__) . '/translator/main.class.php';
    It will load the translator's main PHP file.

    The code dirname(__FILE__) returns the current file's folder, and then is concatenated to build the whole path to the main PHP file. In this example, the translator folder is placed in the same folder as the webpage.php file.

    If the specified path is wrong, you will get an error message like this one:

    Warning: require_once(/help/project/step_6/a_wrong_path/translator/main.class.php) [function.require-once]: failed to open stream: No such file or directory in /help/project/step_6/webpage.php on line 58

    Fatal error: require_once() [function.require]: Failed opening required '/help/project/step_6/a_wrong_path/translator/main.class.php' (include_path='.:/usr/share/php:/usr/share/pear') in /help/project/step_6/webpage.php on line 58

7. Changing the translator's folder location

  • Create a new folder named plugins and move in the translator's folder (/help/project/step_7/):
  • Modify the initialization lines (/help/project/step_7/webpage.php):

    <!-- translator begins -->
    <?php
    require_once dirname(__FILE__) . '/plugins/translator/main.class.php';
    TranslatorManager::initialize('
        css = plugins/translator/_styles/main.css
        js = plugins/translator/_javascript/translator.class.js
        skins_css_folder = plugins/translator/_styles/skins/
        skins_image_folder = plugins/translator/_images/skins/
        flags_folder = plugins/translator/_images/flags/
    ');
    ?>
    <!-- translator ends -->
  • Before (/help/project/step_6/webpage.php):
  • After (/help/project/step_7/webpage.php):
  • Relative paths vs Absolute paths:

    All the above settings: css, js, skins_css_folder, skins_image_folder, flags_folder are going to be used by the internet browser. This means that the specified paths are going to be either relative or absolute on the client side.

    Taking the current project sample, the webpage.php path could be (depends of course where the files are uploaded): http://my_test_server.com/help/project/step_7/webpage.php

    The plugins/translator/_styles/main.css relative path (since it doesn't start with a slash "/") is interpreted by the internet browser like this:
    • Extract the current path from the URL: http://my_test_server.com/help/project/step_7/webpage.php
    • Extracted path: http://my_test_server.com/help/project/step_7/
    • Build the new path: http://my_test_server.com/help/project/step_7/ + plugins/translator/_styles/main.css
    • Final path: http://my_test_server.com/help/project/step_7/plugins/translator/_styles/main.css
    Relative paths are good if the files are being moved, or don't really know nor care where are they.

    If the files and folders are well organized, then an absolute path could be specified, for instance: /plugins/translator/_styles/main.css is interpreted by the internet browser like this:
    • Since the path is an absolute path (starts with a slash "/"), the / path is: http://my_test_server.com/
    • Build the new path: http://my_test_server.com/ + plugins/translator/_styles/main.css
    • Final path: http://my_test_server.com/plugins/translator/_styles/main.css
    In this example, the translator's main folder should be placed inside of plugins folder on the server's root folder.

8. Modifying the default settings

  • The translator comes with a set of default settings. They are defined in the translator/_classes/config.class.php file (/help/project/step_8/plugins/translator/_classes/config.class.php).
    All the default settings can be changed, either in this file or when the translator is being initialized like in the previous example.
  • Modify the initialization line to align to the right side, change the skin and display specific languages organized in 4 columns (http://my_test_server.com/help/project/step_8/webpage.php):

    <!-- translator begins -->
    <?php
    require_once dirname(__FILE__) . '/plugins/translator/main.class.php';
    TranslatorManager::initialize('
        css = plugins/translator/_styles/main.css
        js = plugins/translator/_javascript/translator.class.js
        skins_css_folder = plugins/translator/_styles/skins/
        skins_image_folder = plugins/translator/_images/skins/
        flags_folder = plugins/translator/_images/flags/
        align = right
        languages = Japanese, Korean, Latvian, Lithuanian, Macedonian, Malay, Maltese, Norwegian, Persian, Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swahili, Swedish, Thai
        skin = cyan_classic_compressed
        tab.cols = 4
    ');
    ?>
    <!-- translator ends -->
  • Before (/help/project/step_7/webpage.php):
  • After (/help/project/step_8/webpage.php):
  • Open on the browser:
  • Find all the information about the settings in the reference.
  • Find all the information about the skins in the skins reference.

9. Selecting areas to translate and to exclude from translation

  • Modify the initialization line to specify the target_selectors and the exclude_selectors settings:

    <!-- translator begins -->
    <?php
    require_once dirname(__FILE__) . '/plugins/translator/main.class.php';
    TranslatorManager::initialize('
        css = plugins/translator/_styles/main.css
        js = plugins/translator/_javascript/translator.class.js
        skins_css_folder = plugins/translator/_styles/skins/
        skins_image_folder = plugins/translator/_images/skins/
        flags_folder = plugins/translator/_images/flags/
        align = right
        languages = Japanese, Korean, Latvian, Lithuanian, Macedonian, Malay, Maltese, Norwegian, Persian, Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swahili, Swedish, Thai
        skin = cyan_classic_compressed
        tab.cols = 4
        target_selectors = translate
        exclude_selectors = dont_translate
    ');
    ?>
    <!-- translator ends -->
  • Before (/help/project/step_8/webpage.php):
  • After (/help/project/step_9/webpage.php):
  • Modify the XHTML code to set the headers "My webpage" and "The first car" to be translated, by adding the class attribute (/help/project/step_9/webpage.php):
  • Open on the browser and translate:
  • Modify the XHTML code to translate the whole page, by adding the class attribute to the body tag (/help/project/step_9/webpage.php):
    (The previously added class attributes can be deleted since they are contained in the body tag)
  • Open on the browser and translate:
  • Modify the XHTML code to exclude the headers "My webpage" and "The first car" from the translation (/help/project/step_9/webpage.php):
  • Open on the browser and translate:

10. Adjusting the layout

  • Modify the XHTML and CSS code to separate the translator from the "The first car" header/ Before (/help/project/step_9/webpage.php):
  • After (/help/project/step_10/webpage.php):
  • Open on the browser:

11. Watch the video



Find all the information about the settings in the reference.
Find all the information about the skins in the skins reference.

Translator Revolution PRO | Copyright © 2012 Sur Studio.