Fixed
Details
Priority
MinorAssignee
AlexAlexReporter
AlexAlexDeveloper
AlexAlexChange Log Message
Refactoring Countries and States functionality and adding management optionsPatch Instructions
Patches must be submitted through Phabricator.
To submit patch via Command Line use Patches Workflow (via Arcanist) tutorial.
To submit patch via Web Interface use Patches Workflow (via Web Interface) tutorial.
External issue ID
279External issue URL
Fix versions
Details
Details
Priority
Assignee
Alex
AlexReporter
Alex
AlexDeveloper
Alex
AlexChange Log Message
Refactoring Countries and States functionality and adding management options
Patch Instructions
Patches must be submitted through Phabricator.
To submit patch via Command Line use Patches Workflow (via Arcanist) tutorial.
To submit patch via Web Interface use Patches Workflow (via Web Interface) tutorial.
External issue ID
279
External issue URL
Fix versions
Created September 9, 2009 at 12:01 PM
Updated December 30, 2024 at 2:24 AM
Resolved July 22, 2010 at 8:06 PM
Currently we have around 400 phrases of for countries and states used for ex. during checkout process. Translation of such kind of phrases almost never got changed and they provide additional load to each template, because they are used for Country field for users and user object is loaded on every page and these phrase with it.
I propose to create multilingual column Translation in StdDestinations table and move all current state/country translations there. Then loading of these moved values should be done using "options_sql" option in field definition in unit config.
Later we can add separate grid, where administrators could enable/disabled unneeded countries/states and change their translation.