Application Android - DoliDroid FR: Difference between revisions

Jump to navigation Jump to search
Line 63: Line 63:


Vous pouvez aussi récupérer les sources, par téléchargement anonyme, via le lien qui se trouve dans le menu "A propos" de l'application DoliDroid.
Vous pouvez aussi récupérer les sources, par téléchargement anonyme, via le lien qui se trouve dans le menu "A propos" de l'application DoliDroid.
=Troubleshooting =
== JSERR001 ==
If you get this error when loaing a page/feature with DoliDroid (including tha login page), this means your Dolibarr installation on server side serve bugged pages. In a common usage of Dolibarr, this may have no visible effect for user. But when used from a smartphone, this make DoliDroid fails loading pages.
This is common things to check to solve the problem:
* If you have installed external modules, try after disabling them (some external modules introduce bugs).
* Try also to call login page from a standard PC by adding &dol_use_jmobile=1 as parameter of URL and check you don't have any javascript errors.
* If you installed Dolibarr with the debian package, check into directory '''/usr/share/javascript''' that you find a directory called '''jquery''', '''jquery-ui''' and '''flot'''. If one of this directory is missing (or if all directory '''/usr/share/javascript''') is missing:
- Install missing packages by launching from command line
<source lang="bash">
sudo apt-get install javascript-common libjs-jquery libjs-jquery-ui libjs-flot
sudo apt-get install -f
</source>
- Go into config file '''/etc/dolibarr/conf.php''' and check you have the following line uncommented (if line is not found, add it at end of file).
<source lang="ini">
$dolibarr_js_JQUERY_FLOT='/javascript/flot';
</source>
* If you installed Dolibarr with the debian package, check into directory '''/usr/share/javascript/flot''' that you find a file called '''jquery.flot.pie.js'''. If file does not exists, ...
== Echec de connection ==
Si vous échouez à vous connecter, alors que vous êtes sur que votre login et mot de passe entré (et éventuellement code captcha) est correct, vérifiez auprès de votre hébergeur que l'url que vous utilisez est bien l'URL directe et non une redirection vers l'URL réelle de votre instance.

Navigation menu