Babel create translation and set different templates according to contexts

90 Posts

Edski Reply #1, 15 years, 4 months ago

I have 3 contexts (web) (en) and (de) all context have different templates:
(web) has template "Web Template"
(en) has template "EN Template"
(de) has template "DE Template"

When you create a translation with the "Create translation" button from the Babel Extra it takes the template from the context from where you create the translation.

So when you create a translation via (web) context for (en) context, It gives the created translation the template "Web Template" but I would like it to give it the template "EN Template"

Is this possible?

284 Posts

novolo Reply #2, 15 years, 4 months ago

You might have to edit the plugin here:

					$newResource = $babel->duplicateResource($resource, $contextKey);
					if($newResource) {										
						$linkedResources[$contextKey] = $newResource->get('id');
						$babel->updateBabelTv($linkedResources, $linkedResources);
					} else {
						/* error: translation could not be created */
						$errorParameter = array('context' => $contextKey);
						throw new Exception('error.could_not_create_translation');
					}

It only duplicates (with all settings) the resource.

MODX Free Template Base: MODX-Boilerplate | my blog (lots of MODX stuff) | my gitHub (translations) | MODX User Groups Germany (Facebook)

90 Posts

Edski Reply #3, 15 years, 4 months ago

Thanks Novolo, I also posted to Mikrobi at his blog maybe he will make it work in future releas.

☆ A M B ☆
3,141 Posts

Mark Hamstra Reply #4, 15 years, 4 months ago

What’s the differences in those templates?

Perhaps you can make clever use of context settings or lexicons to narrow it down to just one template? Context setting for a logo for example.

Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.

90 Posts

Edski Reply #5, 15 years, 4 months ago

Mostly headers and footers and some getResourceField with tv’s per language context

☆ A M B ☆
571 Posts

romain Reply #6, 15 years, 4 months ago

I would second Mark here, you can do it like

[[$nav-[[!++cultureKey]]]]
…
[[$footer-[[!++cultureKey]]]]

@modx_fr | Github | modx.fr
@rtripault | Github | melting-media.com

90 Posts

Edski Reply #7, 15 years, 4 months ago

Thanks Guys!

☆ A M B ☆
179 Posts

mindeffects Reply #8, 15 years, 4 months ago

Use the lexicon, like:
[[%key? &topic=`topicname` &namespace=`namespace_name` &language=`en`]]

Example long:
[[%welcome? &topic=`messages` &namespace=`myprojectname` &language=`en`]]

Change the cultureKey system setting with a plugin binded to "OnInitCulture" and you can drop the "&language=". You can forget about "&topic=" if you do nat have a large number of entries which need to have a little organisation.

Example short:
[[%welcome? &namespace=`myprojectname`]]

For "en" you set the value to: "Welcome!"
For "de" you set the value to: "Willkommen!"

More in the docs (http://rtfm.modx.com/display/revolution20/Internationalization)

best
Oliver

MINDEFFECTS – DESIGN for PRINT, WEB and MEDIA
http://twitter.com/mindeffects · http://www.facebook.com/mindeffects · http://www.youtube.com/mindeffects/ · skype://mindeffects_oliver