We support multi language for packages and package groups, but not config options and config option groups. We should add support for this.

We will need to create the following tables

• package_option_language
  • package_option_id INT(10) UNSIGNED NOT NULL
  • lang VARCHAR(5) NOT NULL
  • name VARCHAR(255) NOT NULL
  • description VARCHAR(255) NOT NULL
• package_option_group_language
  • package_option_group_id INT(10) UNSIGNED NOT NULL
  • lang VARCHAR(5) NOT NULL
  • name VARCHAR(255) NOT NULL
  • description VARCHAR(255) NULL DEFAULT NULL

Each config option/group add/edit page will need to be updated with the usual language tabs.

The PackageOptions and PackageOptionGroups models will need to be updated to support adding/fetching these multi-lingual definitions.

• Validation rules should be added to ensure that all languages have names

A migration should be created to add the existing names/definitions to the new table under the company's default language.

A solution will need to be devised for multilingual package option values (i.e. radio/select options)