search

dkd / php-cmis-client

This is a PHP CMIS Client implementation based on OpenCMIS. It has been retired and put in to archive mode.
Apache License 2.0
54 stars 35 forks source link

GuzzleHttp Exception[ParseException]: Unable to parse JSON data #31

Closed selva12 closed 7 years ago

selva12 commented 7 years ago

After configure CMIS connection i clicked the Browse link, then site displays "The website encountered an unexpected error. Please try again later". I found the error in recent logs and i enclosed error details which i am facing. Please give a solution for this. cmis_connection_drupal_8 d8_cmis_issue

ksjogo commented 7 years ago

The message is saying that it got invalid JSON from the server which should not happen and (probably) is not to be fixed on our library side (like invalid request). Which CMIS server are you using and could you look into his logs.

selva12 commented 7 years ago

Thankyou, i will check once. I am using Alfresco 3.4.11 with drupal 8 using this CMIS module. I gave **<root>alfresco/service/cmis** in CMIS browser url. After saving this with login credentials i clicked the Browse link then only that Guzzle error(above mentioned) occurs. I think Alfresco >5 versions are configured properly, i am not sure. So its possible to connect Alfresco 3.4.11 with this module?

ksjogo commented 7 years ago

Afair browser bindings were introduced with version 4.something http://ecmarchitect.com/archives/2013/09/15/3554

selva12 commented 7 years ago

Thankyou for your info, but i need that for Alfresco 3.4 versions not for Alfresco >4 versions. I can able to connect 3.4.d with drupal 7 using CMIS module. Now i need to connect 3.4.d with D8. Please give solutions for that.

ksjogo commented 7 years ago

It seems the D8 cmis module updated to use our library for CMIS. Our library is requiring the browser bindings. You could revert the changes in the D8 module. Or pick some other underlying lib. Or update to a newer Alfresco.

sascha-egerer commented 7 years ago

The implementation is very flexibale and other Bindings can be implemented if required. Feel free to do that. I think form our side there is currently no reason to implement another binding than the Browser Binding. I would suggest to close that issue as it is no issue. We can create a Feature Issue "Add AtomPub Binding" or "Add WebService Binding" if required