Bug 922178 - Vibe4.0_LOC:ALL:Untranslated strings "This plugin is missing the..."appear on "Extensions" dialog Vibe Web Management Console
Summary: Vibe4.0_LOC:ALL:Untranslated strings "This plugin is missing the..."appear on...
Status: VERIFIED INVALID
: 951972 (view as bug list)
Alias: None
Product: Vibe
Classification: Micro Focus Vibe
Component: Administration (show other bugs)
Version: 4.0 (Hudson)
Hardware: x86 Windows 7
: P3 - Medium : Normal
Target Milestone: 4.0 (Hudson)
Assignee: Bohumir Suchomel
QA Contact: Bohumir Suchomel
URL:
Whiteboard:
Keywords: All_Languages, L10N
Depends on:
Blocks:
 
Reported: 2015-03-13 06:58 UTC by Cindy Li
Modified: 2015-10-26 12:40 UTC (History)
2 users (show)

See Also:
Found By: Localization
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Untranslated strings_ENU.png (10.90 KB, image/png)
2015-03-13 06:59 UTC, Cindy Li
Details
Untranslated strings_FR.png (11.77 KB, image/png)
2015-03-13 06:59 UTC, Cindy Li
Details
agents.png (18.38 KB, image/png)
2015-03-14 03:15 UTC, Bohumir Suchomel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Cindy Li 2015-03-13 06:58:45 UTC
Configuration:
Server OS: SLES12 x64
SQL version: MySQL 5.6 
Vibe server build: 20150310183948

Desktop OS: Win 7 Ent. SP1 32bit
Web browser: Firefox 36

Steps to reproduce:
1. Log in to Vibe WebConsole as admin
2. Expand "<user_name>" link and click "Administration Console" link
3. Under Management, click Extensions
4. Click "Add a new extension" on the "Extensions" dialog
5. Click "Browse" and open "Desert,jpg" file from "Libraries > Pictures > Sample Pictures"
6. Click Add 


Actual result: 
Untranslated strings "This plugin is missing the..." appear on "Extensions" dialog Vibe Web Management Console.

Expected result: 
The strings "This plugin is missing the..." should be translated.
Comment 1 Cindy Li 2015-03-13 06:59:13 UTC
Created attachment 626715 [details]
Untranslated strings_ENU.png
Comment 2 Cindy Li 2015-03-13 06:59:27 UTC
Created attachment 626716 [details]
Untranslated strings_FR.png
Comment 3 Forgotten User 9PoxeohwoU 2015-03-13 18:15:31 UTC
FYI:  I researched from a coding perspective and this is nothing that localization can do anything about.  Although the string is properly marked for localization and localized, at the point the string is pulled from the resources, the code is running as the built-in Job Processing Agent user and NOT as the logged in user.  The string will get pulled using whatever locale is defined for the Job Processing Agent user.
Comment 5 Bohumir Suchomel 2015-03-14 03:14:58 UTC
Hi Dennis,
I would like to verify workaround you described in comment 3. Could you please how to change locale of "Job Processing Agent user"? I changed locale of three "agent" users in Admin Console > Users but it didn't work. I guess it didin't work since none of them was "Job Processing Agent" :-)

see screenshots showing three agents users i found in Admin Console.
Comment 6 Bohumir Suchomel 2015-03-14 03:15:23 UTC
Created attachment 626895 [details]
agents.png
Comment 7 Forgotten User 9PoxeohwoU 2015-03-16 16:40:16 UTC
Unfortunately, you currently CANNOT change the locale of the Job Processing Agent user without modifying the database manually.  That user object is currently NOT indexed, hence it doesn't show up in the user management page which is where you would typically set its profile attributes, including locale.

Otherwise, I believe the Job Processing Agent user is set with the systems default locale during the initial setup of a Vibe installation.
Comment 8 Bohumir Suchomel 2015-03-17 02:08:07 UTC
(In reply to Dennis Foster from comment #7)
> Otherwise, I believe the Job Processing Agent user is set with the systems
> default locale during the initial setup of a Vibe installation.


You're right. This bug is not reproducible if we change locale from English to some other supported language during initial set up of Vibe.

Closing as Invalid.
Comment 9 Bohumir Suchomel 2015-03-17 02:08:20 UTC
closing.
Comment 10 Forgotten User 9PoxeohwoU 2015-10-26 12:40:28 UTC
*** Bug 951972 has been marked as a duplicate of this bug. ***