Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0003993 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| feature request | [Openbravo ERP] 01. General setup | major | always | 2008-06-16 17:59 | 2011-02-04 09:16 | ||||||
| Reporter | plujan | View Status | public | ||||||||
| Assigned To | rmorley | ||||||||||
| Priority | normal | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
| Projection | none | ETA | none | Target Version | |||||||
| OS | Windows | Database | Oracle | Java version | don't know | ||||||
| OS Version | XPsp2 | Database version | XE | Ant version | don't know | ||||||
| Product Version | 2.40alpha-r3 | SCM revision | |||||||||
| Review Assigned To | |||||||||||
| Web browser | |||||||||||
| Modules | Core | ||||||||||
| Regression level | |||||||||||
| Regression date | |||||||||||
| Regression introduced in release | |||||||||||
| Regression introduced by commit | |||||||||||
| Triggers an Emergency Pack | No | ||||||||||
| Summary | 0003993: AT240r3 - It is possible to import/export languages for mixed Entities | ||||||||||
| Description | It is possible to choose an Entity for Import / Export process. But you can, by example, export language for System and then import it with BigBazaar (see attach). This will not raise any error, but it will cause an odd behaviour (translation tables keep with new language in english) | ||||||||||
| Steps To Reproduce | 1. Go Languages 2. Search for Italian (Italy) 3. Mark it as System Language and click on Verify Languages 4. Go Import/Export languages, choose System and italian. Export. 5. Replace exported language by italian language pack downloaded from sourceforge. 6. Go Import/Export languages, choose Bigbazaar and italian. Import. 7. Recompile the application 8. When you log in again, if you change app language to Italian you will see everything in english. This will not happen if you choose System on step 6, but you will get not feedback about doing something wrong. | ||||||||||
| Proposed Solution | Solution 1 (just a simple workaround): System should be always default option Solution 2: I do not know why should I ever want to import a language just for a specific client, but this functionality should be revised. I would recommend to separate System import/export from Entity-specific. And also, if an Entity import does not expect a System exported language file, an error should be raised to feedback user. | ||||||||||
| Tags | translation | ||||||||||
| Attached Files |  r240r3_BUG_ImportExportLanguage240.JPG [^] (70,836 bytes) 2008-06-16 17:59
| ||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2008-06-16 17:59 | plujan | New Issue | |
| 2008-06-16 17:59 | plujan | Assigned To | => cromero |
| 2008-06-16 17:59 | plujan | File Added: r240r3_BUG_ImportExportLanguage240.JPG | |
| 2008-06-17 11:23 | pjuvara | Assigned To | cromero => pheenan |
| 2008-06-17 11:23 | pjuvara | Type | defect => feature request |
| 2008-06-17 11:23 | pjuvara | Target Version | => 2.50 |
| 2008-06-19 09:20 | pjuvara | Relationship added | blocks 0004058 |
| 2008-06-19 09:20 | pjuvara | Status | new => acknowledged |
| 2008-06-24 18:29 | pjuvara | Target Version | 2.50 => |
| 2008-06-25 08:53 | pheenan | Tag Attached: translation | |
| 2008-07-01 17:56 | anonymous | sf_bug_id | 0 => 2007959 |
| 2008-11-16 07:44 | pjuvara | Assigned To | pheenan => pjuvara |
| 2011-02-04 09:16 | jpabloae | Assigned To | pjuvara => rmorley |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |