[
https://issues.apache.org/jira/browse/OFBIZ-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-4016:
--------------------------------------
Assignee: Jacques Le Roux
> Changing the locale (language) from the 1st screen of Order Entry is faulty
> ---------------------------------------------------------------------------
>
> Key: OFBIZ-4016
> URL: https://issues.apache.org/jira/browse/OFBIZ-4016
> Project: OFBiz
> Issue Type: Bug
> Components: ALL APPLICATIONS
> Affects Versions: Release Branch 10.04, jQuery, SVN trunk
> Environment: Windows + Chrome or Safari or Opera or IE8 (also Firefox
> for jQuery)
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
>
> From this URL https://demo-trunk.ofbiz.apache.org/ordermgr/control/orderentry
> if you try to change the language, at return you get a blanck screen with the
> current logged in user login and description.
> This is because
> * ListLocales request uses save-last-view
> * and setSessionLocale uses view-last
> In the (not so specific) case of orderentry request, it happens that the last
> request is not orderentry but the last lookup request done from this screen
> (LookupUserLoginAndPartyDetails with admin, LookupCustomerName with
> flexadmin). So a good solution would be to have the lookups requests fired
> inside the main request (here LookupUserLoginAndPartyDetails and
> LookupCustomerName inside orderentry). Not sure yet if it's possible. I'd
> like to keep the automatic return to calling screen behaviour (and BTW extend
> it to Themes and TimeZones), else we will have to use the same behaviour than
> for Themes and TimeZones currently: manual return :(
> This is not specific to orderentry but to each screen which has at least a
> lookup and uses the lookup description mechanism. Actually it's even wider
> than that since it implies save-last-view+view-last and a lookup+description.
> Note that, for a still obscure reason (autocomplete not OFF or not working?),
> I don't reproduce this in Firefox (on Windows) for the trunk, either locally
> or from demo because the lookup description mechanism is not working. But I
> reproduces with jQuery branch which is from where I detected and identified
> the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
