Extras catalogue

Translations

Latest release 14 years ago (September 17, 2012).

translations

  • By alanpich

About

Offer translated versions of your resources without having to maintain multiple trees and/or contexts. All translations of a resource are managed direct from the native resource edit view in the manager. Visitor's browser language is automatically detected and if the requested resource has a translation in that language then it is served to them transparently.

Designed to work transparently with other existing and future components including getResources and Quip.

Installation & usage

Install package via package manager(will complete, but show error creating DB model)

Re-install package again (this time db table will create succesfully?!?!?!?!?!)

Attach OnHandleRequest event to plugin Translations/TranslationGateway

Create a Translated Document as you would a normal resource. Save.

Once the page has refreshed, switch to the Translations tab and select New Translation

Pick your language from the dropdown (This lists all languages currently in the lexicon)

Add your content to the translation fields

Visit the page in your browser.

NOTE: Language Switching is set by your browser's request language. It can be overridden by explicitely setting the GET param language (i.e http://www.example.com/?id=123&language=fr)

If a translation does not exist in the requested language, the main resource language will be used

At a glance

MODX 3 compatibility unknown. Based on our testing and community reports where available.

  • Developer alanpich
  • Latest release September 17, 2012 (14 years ago)
  • First seen in SiteDash September 14, 2012 (14 years ago)
  • License GPLv2
  • MODX support 2.2 – 100.0

Releases 1 indexed release

Changelog
MODX.com

1.0-beta1

 September 17, 2012

14 years ago

 —