IMO current SGL_Translation functionality is poor to build real multilingual sites easy. In every manager a developer has to identify same languageID, pageID, fallback language etc. SGL_ItemTranslation tries to ease the development of multilingual managers and is built on top of SGL_Translation.

Sure, the SGL_ItemTranslation implementation is not the best way to extend SGL_Translation and must be improved or maybe totally discarded, but it still could help to simplify your life.


Building new manager a developer identifies:

  • pageID for a manager's item,
  • table fields (also required fields) to translate by translation class,
  • validation code (in !ManagerName::validate()).

Other operations (SGL_Translation methods calls) are left to SGL_ItemTranslation. Typically a website requires just several languages to operate with. This class provides a way to edit all content versions (all languages) at the time. But that doesn't mean, that a webmaster has to fill all content (for all languages) at one time. The only values, that must be identified, are required fields of fallback language. In case a webmaster entered just a fallback translation, but current language is not a fallback one, all required fields values will be replaced with values of fallback language. Non-required fields are left blank.


The best way to understand how it works is to try.

  • unpack attached archive,
  • copy files to SGL dirs,
  • (re)install SGL,
  • login as admin,
  • go to http://path-to-sgl/index.php/transdemo/testadmin/.

Transdemo is a demo module, which was created by ModuleGenerator with custom generation templates and then extended to use SGL_ItemTranslation functionality. The demo table has two fields to work with: name and description, where name field is required.


  • All languages have to be converted to same encoding i.e. UTF-8, otherwise there is no sense to use this class.
  • SGL_ItemTranslation::translateAll() method is quite heavy one for DB, 'cos it queries database as many times, as many records it tries to translate (I have an idea how to avoid this.)
  • This class is experimental and may not solve your problems. As mentioned above, SGL gurus may totally reject the way it works and suggest another solution. Anyway all comments are welcome.
  • Do not use provided transdemo module if my imagedemo module is installed. Both modules have the same test manager. :)


Code examples


require_once dirname(__FILE__) . '/DA_Transdemo.php';
    function validate($req, &$input)
        $this->init(); // init lang translation support
        if ($input->submitted) {
    function init()
        $this->tr = & new SGL_ItemTranslation(SGL_MODULE_TRANSDEMO_TRANSID_ITEM);
        $this->tr->setFields(array('name', 'description'));
        $this->tr->setFields(array('name'), $required = true);

List data

    function _cmd_list(&$input, &$output)
        $aPagedData = SGL_DB::getPagedData($this->dbh, $query, $pagerOptions);
        if (!empty($aPagedData['data'])) {
            $this->tr->translateAll($aPagedData['data']); // HEAVY !!!
            $output->aPagedData = $aPagedData;
            $output->pager      = $aPagedData['totalItems'] > $limit;

Insert data

    function _cmd_insert(&$input, &$output)
        // prepare translation / set fallback
        $oItem = &DB_DataObject::factory($this->conf['table']['trans_demo']);
        // insert translation

Delete data

    function _cmd_delete(&$input, &$output)
        foreach ($input->aDelete as $id) {
            $oItem = &DB_DataObject::factory($this->conf['table']['trans_demo']);
            // delete translation