|
In-Portal Issue Tracker - In-Portal CMS
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Type: | Reproducibility: | Date Submitted: | Last Update: |
| 670 | [In-Portal CMS] Data Management | feature request | N/A | 2010-03-27 18:11 | 2010-03-27 18:11 |
|
|
|||||
| Reporter: | BaSSiST | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | active | Product Version: | 5.0.3-B1 | ||
| Product Build: | Resolution: | open | |||
| ETA: | none | Fixed in Version: | |||
| Reference: | http://groups.google.com/group/in-portal-dev/browse_thread/thread/98056ee228200ba0 | ||||
| Change Log Message: | |||||
| Estimate Points: | 0 | ||||
|
|
|||||
| Summary: | 0000670: Replace kMultiLanguage formatter with 'multilang' field option | ||||
| Description: |
My suggestion is simple - to remove kMultiLanguage formatter and add 'multilang' field option (in unit config). Why? Because there are some cases when you need to apply any formatter (different from kMultiLanguage) to field, but field also needs to be multi-language. For example, in banner management system you may need to upload different images for each language. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
|
|
|||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2010-03-27 18:11 | alex | Reporter | alex => BaSSiST | ||
| 2010-03-27 18:11 | alex | New Issue | |||
| 2010-03-27 18:11 | alex | Reference | => http://groups.google.com/group/in-portal-dev/browse_thread/thread/98056ee228200ba0 | ||
| There are no notes attached to this issue. |