I can connect with openerp 6.1 just fine with apple ipad (first edition ios 5.1.1). I have tried to connect with v7.0 with no success using multiple navigators. I have emptied cache and cookies with no success. The old forum has a similar issue: forum.openerp.com/forum/topic35859.html The page is white.Is anyone having the same connection problems with ipad? Thanks
Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
- CRM
- e-Commerce
- Comptabilité
- Inventaire
- PoS
- Projet
- MRP
Cette question a été signalée
2
Réponses
8887
Vues
1. Close safari, delete history and cookies and do not use in private mode. Try again.
2. Try an other browser.
Cause 1: Possibly there is a timing issue. However in that situation there is a message js:xxxxx with xxxxx is a number. I think iPAD 1 and iPAD 2 will have timing issues.
Cause 2: Browser language issues. If you didn't update IOS and browsers to recent versions the browser is not compatible. The new browser language OpenERP 7.0 clientsoftware uses is so much changed, an old browser doesn't understand it. Blank screens and doing nothing can be the result of this.
Check:
1. Which version of the iPad are you using?
2. Which version of IOS?
3. Which version of the browser are you using?
That did not work on my old iPad on both Safari and Chrome. I think OpenERP web does not work on iPad v1. may be due to the small memory or limitation in iOS v5. It worked fine on iPad v3.
Answer: It does not work because your browser version is outdated.
I am using OpenERP V7 with new ipad with an up to date browser.
Vous appréciez la discussion ? Ne vous contentez pas de lire, rejoignez-nous !
Créez un compte dès aujourd'hui pour profiter de fonctionnalités exclusives et échanger avec notre formidable communauté !
S'inscrire| Publications associées | Réponses | Vues | Activité | |
|---|---|---|---|---|
|
1
oct. 25
|
5634 | ||
|
0
déc. 24
|
10550 | ||
|
3
sept. 24
|
23047 | ||
|
5
déc. 24
|
55182 | ||
|
4
juil. 24
|
11860 |
What browser are you using? Try to change it!
I have updated the question to reflect your suggestion. This does not seem to be the problem.