Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0045733Retail ModulesWeb POSpublic2021-01-14 14:072021-01-20 13:14
Reporterjorgewederago 
Assigned Toranjith_qualiantech_com 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product VersionRR19Q3.3 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customerGold
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0045733: The login page should match the language of the current client
DescriptionIn an instance where we have a server with multi clients configured, whenever any of them access to WebPOS the login page is loaded with the language of the System. However, each client could be configured to use different language (Eg: Spanish or French) and should be displayed in that one.
Steps To Reproduce*Set the language of the client System to English
*Set the language of Client 1 to Spanish or French
*Navigate to a POS Terminal from Client 1

Check that the whole POS Terminal Login page is loaded in English and it should be in Spanish or French.
Proposed SolutionIt should be possible to send the labels of the organization by changing the context. This can be done in all the cases but when we are doing a link terminal and offline scenarios.
Additional Information
TagsNo tags attached.
Relationships
related to defect 0045047 closed ranjith_qualiantech_com Translations in POS are not working 
related to defect 0044157 closed ranjith_qualiantech_com Label translations in POS Login page 
Attached Filesdiff 45733_19Q3.3_mobilecore.diff (1,340) 2021-01-18 13:05
https://issues.openbravo.com/file_download.php?file_id=15258&type=bug
diff 45733_19Q3.3_posterminal.diff (1,489) 2021-01-18 13:05
https://issues.openbravo.com/file_download.php?file_id=15259&type=bug
Issue History
Date ModifiedUsernameFieldChange
2021-01-14 14:07jorgewederagoNew Issue
2021-01-14 14:07jorgewederagoAssigned To => Retail
2021-01-14 14:07jorgewederagoOBNetwork customer => Gold
2021-01-14 14:07jorgewederagoResolution time => 1612393200
2021-01-14 14:07jorgewederagoTriggers an Emergency Pack => No
2021-01-14 14:08jorgewederagoDescription Updatedbug_revision_view_page.php?rev_id=22037#r22037
2021-01-14 14:10jorgewederagoProposed Solution updated
2021-01-18 12:31ranjith_qualiantech_comAssigned ToRetail => ranjith_qualiantech_com
2021-01-18 12:31ranjith_qualiantech_comRelationship addeddepends on 0044157
2021-01-18 12:31ranjith_qualiantech_comRelationship addedrelated to 0045047
2021-01-18 12:31ranjith_qualiantech_comRelationship deleteddepends on 0044157
2021-01-18 12:31ranjith_qualiantech_comRelationship addedrelated to 0044157
2021-01-18 13:05ranjith_qualiantech_comFile Added: 45733_19Q3.3_mobilecore.diff
2021-01-18 13:05ranjith_qualiantech_comFile Added: 45733_19Q3.3_posterminal.diff
2021-01-20 13:14marvintmReview Assigned To => marvintm
2021-01-20 13:14marvintmNote Added: 0125695
2021-01-20 13:14marvintmStatusnew => closed
2021-01-20 13:14marvintmResolutionopen => no change required
2021-01-20 13:15marvintmNote Edited: 0125695bug_revision_view_page.php?bugnote_id=0125695#r22047

Notes
(0125695)
marvintm   
2021-01-20 13:14   
(edited on: 2021-01-20 13:15)
This problem was fixed a long time ago, and doesn't happen in current releases. The patches attached to the issue can be used to fix it in 19Q3.