content aliases, max version 1.2.4

[Chris..S]

The content_aliases module says its max supported CMS MS version is 1.2.4.

Does anyone know if this is actually the case, ie. its broken in 1.2.5 and later, or its just a symptom of the last update to the module in Feb of this year - around the time of 1.2.3 and 1.2.4.

[Dr.CSS]

You've used it in a newer ver. of CMSMS and it didn't work?...

Find the line that calls out the ver. max/min/required and change it and see if that's makes it work...

[alby]

The content_aliases module says its max supported CMS MS version is 1.2.4.

Page Internal Link (Content type in Page editing) is the replace of content_aliases

Alby

[Chris..S]

Thanks for the reply.

Internal page link content type doesn't appear to support use of a different template.  Is that possible?
(any hints on how to accomplish that too )

I use a different template for different languages.  That allows me to have a single main page with the content and its translation(s) and to have each template show the content for its language along with any fixed strings in the language.  Each page can then have a content alias for each translation using the template appropriate for that language.

[alby]

I use a different template for different languages.  That allows me to have a single main page with the content and its translation(s) and to have each template show the content for its language along with any fixed strings in the language.

It's a MLE version?
Best practies is to work on template for use unique template for each languages.

Alby

[Chris..S]

It's a MLE version?
Best practies is to work on template for use unique template for each languages.

Alby

Sorry, I don't understand.  What is MLE?

Do you mean I shouldn't use a unique template for each language?
I can't see how I can simply provide for strings in the template and have them straightforward to translate.

[alby]

It's a MLE version?
Best practies is to work on template for use unique template for each languages.

Sorry, I don't understand.  What is MLE?

Do you mean I shouldn't use a unique template for each language?
I can't see how I can simply provide for strings in the template and have them straightforward to translate.

If you don't use MLE, for other languages to use languages tree but then you have Internal page link in any tree all indipendent from others or not?

Alby

[Chris..S]

I have found the MLE forum and am looking at it now.

Using content aliases, I would have the primary set of page in the major language underneath a section header named after the language.  I would then create section headers for the minor languages and create those pages that were to be present in that language in a menu structure that pretty well mirrors that of the primary language.  Each of those pages would  be a content alias targeting the primary page and using the minor language template.

e.g.

EN
- home page (home-en template)
- about us (standard-en template)

DE
- home page --> EN/home page (home-de template)
- about us --> EN/about us page (standard-de template)

Plus I have a custom tag that can generate the correct link to the same page in another language.

[alby]

EN
- home page (home-en template)
- about us (standard-en template)

DE
- home page --> EN/home page (home-de template)
- about us --> EN/about us page (standard-de template)

Plus I have a custom tag that can generate the correct link to the same page in another language.

But the content in other languages?
If DE/about-us is a content aliases of EN/about-us, you have EN content of EN/about-us?

However, edit ContentAliases.module.php, search:

Code: Select all

	function MaximumCMSVersion()
	{
	return '1.2.4';
	}

and replace 1.2.4 with 1.4.1

Alby

[Chris..S]

Thanks for the note to change the version string.

But the content in other languages?
If DE/about-us is a content aliases of EN/about-us, you have EN content of EN/about-us?

I use content blocks for each language and reference them in a smarty comment at the top of the primary template to ensure they get shown in the admin/page content editor.  I like that this ensures the content for all (normally two) languages is shown on the same editing page.