[fredpeaks]

Hi,

I think you should localize the File model and use the relation to access it.
For example :

 $model->file->path_en 

To achieve this you should configure multilang behavior on the File model and retrieve your data using this type of loading (this example is in the page of the behavior):

$model = Page::model()->multilang()->with('articles', 'articles.multilangArticle')->findByPk((int) $id);
echo $model->articles[0]->content_en;

kailash, on 31 August 2012 - 04:31 AM, said:

Hi,

I don't understand if I can have translated relations.

I have a GalleryFile model which has a belongs_to relation to a File model

 'file' => array(self::BELONGS_TO, 'File', 'file_id') 

The file must be localized in italian and english so I put this in the behavior config array

'localizedAttributes' => array('file_id','other_fields' .. )

Usually I can get the File model using the relation,

$galleryFileModel->file

the nicest thing ever would be to be able to do something like

 $model->file_en 

and get the File which id is the localized english file_id. Is it possibile as now to do something like that ?
Or I have to define a relation for each language?


Regards and thanks to the authors of this excellent extension!

[fredpeaks]

Hi,

I think your form isn't exactly as in the example I give in the behavior page.
If the default language on your site is "en", you should have title, title_el, content and content_el fields (and not title_en, title_el, content_en and content_el).

Maybe you removed this part of the example form code :

if($l === Yii::app()->params['defaultLanguage']) $suffix = '';
else $suffix = '_'.$l;

If this is not the case, I'm surprised by your bug because it is a very common use case and I've never seen this problem.
Maybe you could post your behavior configuration and the rules definition of your model ?

Thanks

antoniom, on 31 August 2012 - 09:37 AM, said:

Hello and thanks for sharing this amazing behavior.

However please notice an issue I found using the behavior. I was trying to add i18n at the post table. Post table has required fields the title and content attributes. The blog should support two languages English (en) and Greek (el).

So i created a form as defined on your example which creates title_en, title_el, content_en and content_el fields. When submitting the form the application returned an error stating that title and content are required!
By examining the behavior I found out that these attributes (title_en, title_el, content_en and content_el) not only they had'nt the "required" validator assigned but the original attributes (title and content) continued to have their own "required" validators.

So I modified the code to remove the "required" validator from the original attribute and add "required" validator the new ones:

	else if($rule[1] === 'required') {
		//We add a safe rule in case the attribute has only a 'required' validation rule assigned
		//and forceOverWrite == false
		//$validators->add(CValidator::createValidator('safe', $owner, $attr . '_' . $l, array_slice($rule, 2)));
		// we do need to add the required property for the new attributes and remove the old required property for 
		$validators->add(CValidator::createValidator('required', $owner, $attr . '_' . $l, array_slice($rule, 2)));
		$validatorList = $owner->getValidatorList();
		
		$i = 0;
		while($i < $validatorList->count) {
			$validator = $validatorList->itemAt($i);
			if( $validator instanceof CRequiredValidator ) {
				$index = array_search($attr, $validator->attributes);
				if ($index !== false) {
                                	unset($validator->attributes[$index]);
                                        $validator->attributes = array_values($validator->attributes);
                                        break;
				}
			}
			$i++;
		}
	}

The above works fine, it may help somone else also.
However, if you think that I missed something, or that something is wrong, let me know.

Thanks!

[antoniom]

fredpeaks, on 31 August 2012 - 11:39 AM, said:

I think your form isn't exactly as in the example I give in the behavior page.
If the default language on your site is "en", you should have title, title_el, content and content_el fields (and not title_en, title_el, content_en and content_el).

Thank you fredpeaks.
That was the case, I did not configured the params['defaultLanguage'] so the $suffix var had always something to get.

Once again, thank you for sharing the class!

[kailash]

Thank you very much fred! However I solved my problem with a different approach..

I felt like experimenting so I modified your code and implemented that feature myself, and now I'm sharing the results, maybe it might help someone or give you some ideas for further development


I added a new property to the behavior

public $localizedRelations;

(I know it's a very unfortunate name as it also exist a $localizedRelation property, but again, it's an experiment)

Then I created a little method to assign relations to the dynamic generated translation model

private function createLocalizedRelations($related)
    {
        if(empty($this->localizedRelations)) return;
        
        $owner_relations = $this->getOwner()->relations();

        foreach($this->localizedRelations as $rel_name )
        {   
            $original_rel = $owner_relations[$rel_name];
                                  
            foreach ($related as $model) 
            {        
                switch ($original_rel[0])
                {
                    case CActiveRecord::BELONGS_TO:
                                               
                        $class = CActiveRecord::BELONGS_TO;
  
                        $model->getMetaData()->relations[$rel_name] = 
                                new $class($rel_name, 
                                           $original_rel[1], 
                                           $this->localizedPrefix.$original_rel[2]); 
                   break;
                }
           }           
        }
    }

It obviously works with belongs_to relations only but it shouldn't be difficult to implement the other relation types as well

This function is called in the afterFind method of the behavior.

I configure the behavior assigning to that property an array with the name of the relations i want to localize

'ml' => array(
 'class' => 'ext.MultilingualBehavior',
                           
  'localizedAttributes' => array('fid', 'link'), 
  'localizedRelations' => array('file'),          
                            
  'languages' => Yii::app()->params['languages'], 
  'defaultLanguage' => Yii::app()->language, 
 )

'file' is the name of a BELONGS_TO relation


After that I can access my localized file model with very little effort

<?php print $model->multilangGalleryFile['en']->file->render()?>

What do you think about it?

(I attached the modified file to the post)

Attached File(s)

•  MultilingualBehavior.php (21.77K)
  Number of downloads: 5

[luca90]

Hi all! It's my first post on Yii forum, so hi all again!
I'm using yii by no long time and i finded this extension.. thanks to all because it's fantastic.
I followed all the point for install and use that, but after long tests i still have a problem.

On the create or update of a record, the record for the default language it's saved in "table" and in "table_lang"

Where i wrong?

Once again, thank you for this fantastic class!

[C.S.Putera]

Hi, thanks for a great extension.

I have successfully saved the translated models, but got error when accessing actionAdmin method :

CDbCommand failed to execute the SQL statement: SQLSTATE[42P01]: Undefined table: 7 ERROR: missing FROM-clause entry for table "i18nannualpurchase"
LINE 1: ...nnual_purchase_id"="t"."annual_purchase_id") AND (i18nAnnual...
^. The SQL statement executed was: SELECT COUNT(DISTINCT "t"."annual_purchase_id") FROM "tbl_annual_purchase" "t" LEFT OUTER JOIN "tbl_annual_purchase_lang" "i18nAnnualPurchase" ON ("i18nAnnualPurchase"."annual_purchase_id"="t"."annual_purchase_id") AND (i18nAnnualPurchase.lang_id='en_us') 

This is my actionAdmin :

public function actionAdmin()
{
        $model = new AnnualPurchase('search');
	$model->unsetAttributes();
	if(isset($_GET['AnnualPurchase']))
		$model->attributes = $_GET['AnnualPurchase'];
	$this->render('index', compact('model'));
}

Here is how I apply the extension on my AnnualPurchase model :

public function behaviors()
{
        return array(
		'ml' => array(
			'class' => 'application.components.behaviors.MultilingualBehavior',
			'langClassName' => 'AnnualPurchaseLang',
			'langTableName' => 'tbl_annual_purchase_lang',
			'langForeignKey' => 'annual_purchase_id',
			'langField' => 'lang_id',
			'localizedAttributes' => array('name'),
			'localizedPrefix' => 'l_',
			'languages' => Yii::app()->params['translatedLanguages'],
			'defaultLanguage' => Yii::app()->params['defaultLanguage'],
			'createScenario' => 'add',
			//'localizedRelation' => 'i18nAnnualPurchase',
			//'multilangRelation' => 'multilangAnnualPurchase',
			//'forceOverwrite' => false,
			//'forceDelete' => true,
			//'dynamicLangClass' => true,
		)
	);
}

I am using PostgreSQL 9.1, where am I missing ? Please help Thanks

[C.S.Putera]

Error fixed by changing line 259 in the MultilingualBehavior.php into :

$owner->getMetaData()->relations[$this->localizedRelation] = new $class($this->localizedRelation, $this->langClassName, $this->langForeignKey, array('on' => '"'.$this->localizedRelation.'"' . "." . $this->langField . "='" . $lang . "'", 'index' => $this->langField));

NOTE : Adding quotation mark before and after $this->localizedRelation

[AndreiCurelaru]

+1 It could be from useful to really a must have for us too !

We have 3 yii big multilanguage projects :-s on fire.

[fredpeaks]

Hi,

Sorry for the time taken to answer, I'm very busy now.
Are you sure that your fix won't break anything for the mysql users ?
I don't want to publish this version if it doesn't work anymore with mysql...
Maybe I can add an option for postgre users or detect the use of postgre in the main config. If you have any idea, that would be cool, I'm not very familiar with postgre.

If someone could test the fix with mysql and post a feedback, it would be great and I could publish it as fast as possible.

Thank you for your work.

C.S.Putera, on 22 November 2012 - 09:57 AM, said:

Error fixed by changing line 259 in the MultilingualBehavior.php into :

$owner->getMetaData()->relations[$this->localizedRelation] = new $class($this->localizedRelation, $this->langClassName, $this->langForeignKey, array('on' => '"'.$this->localizedRelation.'"' . "." . $this->langField . "='" . $lang . "'", 'index' => $this->langField));

NOTE : Adding quotation mark before and after $this->localizedRelation

[Backslider]

guillemc, on 27 November 2011 - 12:36 PM, said:

@Avalon:

No, I'm still using the same database structure (all attributes in the main table, plus translatable attributes in a separate table).

The reason is that it makes it a lot easier to handle missing translations. Having a default or main language allows you to easily fall back to that language in case a translation doesn't exist, without having to make another query.

Far better to have a 'default_language' flag in the second table. Your solution has the same flaw as that by Fred, its just very bad design.

[fredpeaks]

Thanks for your very constructive post Backslider. The default language is defined in the application configuration, no need to put it in the database.
I'm not a fan of having the translated attributes in the main table but have no time to think about a solution to remove them. And by the way, your making a comment about a post that has been posted a year ago and if you had read the other posts, you could have understand that guillemc's work is at the origin of the extension so it's normal that it is the same "very bad design"...
Feel free to post a modified version of the extension with your very good design my programmer lord .

Backslider, on 22 December 2012 - 12:15 PM, said:

Far better to have a 'default_language' flag in the second table. Your solution has the same flaw as that by Fred, its just very bad design.

[C.S.Putera]

Hi Fredpeaks, sorry for the late reply. Haven't tried it with mysql though