[CRM-3349] Localizable properties currently stored in domain.config_backend should be moved to their own tables / columns to support multi-language configurations Created: 24/Jul/08 Updated: 01/Jun/12 Resolved: 01/Jun/12
|Component/s:||Core CiviCRM, Internationalisation|
|Affects Version/s:||2.1, 3.1|
|Reporter:||David Greenberg||Assignee:||Donald A. Lobo|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Money and currency formatting / locale properties and date formatting properties need to be moved from config_backend and put in their own columns (TBD - but would be reasonable to add them as columns to civicrm_preferences / preferences_date - or create preferences_money table.
|Comment by David Greenberg [ 11/Nov/08 ]|
|Moving a batch of less critical issues and import-related fixes to 2.3. The 2.2 release has a tight and fixed deadline.|
|Comment by Donald A. Lobo [ 01/Jun/12 ]|
These 448 issues have not been worked on for the past 18 months.
Doing a bulk close of old issues to make the issue queue more manageable. We should do this on a periodic basis.