Hi Nicolas,

External libraries are pinned down in releases. I don't think Laurent will
be wanting to update it in 4.x.
The next window for updating is 5.x (currently develop) and it seems
already fixed. See https://github.com/Dolibarr/dolibarr/issues/4912

If you use the repository, you should be able to update your version
locally using composer : composer require --no-dev
restler/framework:3.0.0-RC6
Just create a branch before ;)

Regards,

*Raphaël Doursenaud*
Directeur technique (CTO)
Expert certifié en déploiement G Suite
<https://gpcsolutions.fr/raphael-doursenaud-google-apps-certified-deployment-specialist>
+33 (0)5 35 53 97 13 - +33 (0)6 68 48 20 10

2016-10-12 14:30 GMT+02:00 Nicolas Dorigny - datætic <n...@dataetic.fr>:

> Hello,
>
> I upgraded from 3.9.3 to 4.0.1 and I had warnings in the webservice Rest
> explorer (/htdocs/api/admin/explorer.php) and in every webservice call:
>
> Warning: substr() expects parameter 1 to be string, array given in
> htdocs/includes/restler/framework/Luracast/Re
>
> This is a known issue in Luracast/Restler that has been corrected:
> https://github.com/Luracast/Restler/issues/540
>
> I upgraded locally to the latest Luracast/Restler and the warnings
> disappeared.
>
> The library should be updated in Dolibarr sources.
>
> --
> [image: dataetic]
>
> *Nicolas Dorigny*
> Consultant - Développeur web freelance
> n...@dataetic.fr | 05 61 87 01 89 <0561870189> | 06 65 68 44 64 <0665684464>
>
>
>
> _______________________________________________
> Dolibarr-dev mailing list
> Dolibarr-dev@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
>
>

-- 
 <https://gpcsolutions.fr>
https://gpcsolutions.fr
Technopole Hélioparc
2 avenue du Président Pierre Angot
64053 PAU CEDEX 9
SARL GPC.solutions au capital de 7 500 € - R.C.S. PAU 528 995 921
<http://wiki.dolibarr.org/index.php/Dolibarr_suppliers_France#GPC.solutions>
_______________________________________________
Dolibarr-dev mailing list
Dolibarr-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev

Répondre à