Bug 877338 - [pt_BR][SAM Web GUI] - Upload New Manifest showing error improperly, that also not localized
Summary: [pt_BR][SAM Web GUI] - Upload New Manifest showing error improperly, that als...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Subscription Asset Manager
Classification: Retired
Component: katello
Version: 1.2
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Tom McKay
QA Contact: SAM QE List
URL:
Whiteboard:
Depends On:
Blocks: sam12-tracker
TreeView+ depends on / blocked
 
Reported: 2012-11-16 09:48 UTC by Satyabrata Maitra
Modified: 2012-11-30 15:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-30 15:56:07 UTC
Embargoed:


Attachments (Terms of Use)
Manifest error message. (94.03 KB, image/png)
2012-11-16 09:48 UTC, Satyabrata Maitra
no flags Details

Description Satyabrata Maitra 2012-11-16 09:48:51 UTC
Created attachment 646270 [details]
Manifest error message.

Description of problem:
In pt_BR locale, to import manifest, when trying to upload new manifest file (may it is not a proper manifest file or some other file) through browse, it is showing error, but the error message contains the code, instead of pure sentence based error message. And the error message is not at all translated as well.

Version-Release number of selected component (if applicable):
katello-headpin-all-1.2.5-1h.el6_3

How reproducible:
Always.

Steps to Reproduce:
1. Login with pt_BR locale.
2. Go to Contents tab
3. Click on Import Manifest
4. Click on Browse, on the "Upload New manifest" field.
5. Try to upload just any file.
6. Observe the error message showing.
  
Actual results:
The Erroneous error message showing which contains codes, and as well as not translated.

Expected results:
It should show the error message more meaning fully, in sentence, not having any coding in it. And it should be translated as well, in case of native language.

Additional info: Screen shot attached for reference.

Comment 1 Tom McKay 2012-11-30 15:56:07 UTC
The cause of this error is fixed in a newer compose. The error message itself, being from a backend engine, will not be translated.


Note You need to log in before you can comment on or make changes to this bug.