Openbravo Issue Tracking System - Retail Modules
View Issue Details
0028688Retail ModulesOffline Modepublic2015-01-20 12:532016-03-10 20:21
lorenzofidalgo 
marvintm 
normalmajoralways
closedno change required 
5
main 
 
Orekaria
No
0028688: Impossible to login after clearing cache
If you have your cache cleared before trying to login, POS gets stuck trying to login.
No error shown, just stuck.
Console shows the following errors:

forcibly closing database ?terminal=CMS-1:1

POST http://localhost:8080/openbravo/org.openbravo.retail.posterminal/POSLoginHandler [^] net::ERR_NAME_RESOLUTION_FAILED enyo.js:953enyo.xhr.request enyo.js:953enyo.kind.request enyo.js:1017enyo.kind.go enyo.js:1009OB.Model.Terminal.Backbone.Model.extend.login 7abb96b34b5cab67da0777a076174c5b_WebPOS.js:229enyo.kind.loginButtonAction 7abb96b34b5cab67da0777a076174c5b_WebPOS.js:271enyo.kind.inputKeydownHandler 7abb96b34b5cab67da0777a076174c5b_WebPOS.js:270enyo.kind.dispatch enyo.js:628enyo.kind.delegateEvent enyo.js:624enyo.kind.bubbleDelegation enyo.js:621enyo.kind.delegateEvent enyo.js:624enyo.kind.bubbleDelegation enyo.js:621enyo.kind.delegateEvent enyo.js:624enyo.kind.bubbleDelegation enyo.js:621enyo.kind.delegateEvent enyo.js:624enyo.kind.bubbleDelegation enyo.js:621enyo.kind.delegateEvent enyo.js:624enyo.kind.bubbleDelegation enyo.js:621enyo.kind.delegateEvent enyo.js:624enyo.kind.bubbleDelegation enyo.js:621enyo.kind.dispatchEvent enyo.js:613enyo.kind.inherited enyo.js:410enyo.kind.dispatchEvent enyo.js:1338enyo.kind.dispatchBubble enyo.js:616enyo.kind.bubble enyo.js:604enyo.dispatcher.dispatchBubble enyo.js:1783enyo.dispatcher.dispatch enyo.js:1762enyo.dispatch"
Go login screen.
Clear cache.
Try to login.
POS will get stuck "Loading..."
No tags attached.
related to defect 0022788RMP19 closed marvintm Login offline at first time, window remains Loading... 
png Blocked Login.png (256,171) 2015-01-20 12:54
https://issues.openbravo.com/file_download.php?file_id=7705&type=bug
png
Issue History
2015-01-20 12:53lorenzofidalgoNew Issue
2015-01-20 12:53lorenzofidalgoAssigned To => marvintm
2015-01-20 12:53lorenzofidalgoFile Added: Blocked Login.png
2015-01-20 12:53lorenzofidalgoTriggers an Emergency Pack => No
2015-01-20 12:53lorenzofidalgoRelationship addedrelated to 0022788
2015-01-20 12:53lorenzofidalgoFile Deleted: Blocked Login.png
2015-01-20 12:54lorenzofidalgoFile Added: Blocked Login.png
2015-01-20 14:35lorenzofidalgoDescription Updatedbug_revision_view_page.php?rev_id=7489#r7489
2015-01-20 14:36lorenzofidalgoDescription Updatedbug_revision_view_page.php?rev_id=7490#r7490
2016-03-10 20:21OrekariaReview Assigned To => Orekaria
2016-03-10 20:21OrekariaNote Added: 0084882
2016-03-10 20:21OrekariaStatusnew => closed
2016-03-10 20:21OrekariaResolutionopen => no change required

Notes
(0084882)
Orekaria   
2016-03-10 20:21   
The user should never clear the cache. If clear cache is required then IT would be a major issue, but not being able to login after clearing the cache and not refreshing is not an issue but a wrong practice