Problem parsing JSON in Chromium 59

Any issues about docs (uploading, editing and etc.)
Post Reply
PurpleAlien
Posts: 2
Joined: Thu Jun 22, 2017 11:25 pm

Problem parsing JSON in Chromium 59

Post by PurpleAlien » Thu Jun 22, 2017 11:35 pm

Hi all,

I'm running Onlyoffice Version 9.0.0.300. I recently updated Chromium on client side to version 59 (59.0.3071.104 developer build).
I'm seeing the following in the console, which prevents me to opening any document or folder:

Code: Select all

Error parseJSON: 

                  {
                  "entryType": "folder",
                  "access": 0,
                  "create_by_id": "9db9cd5e-cd54-11e6-a7a1-0242ac12000415/06/2017 00:3422/06/2017 22:18falseppt0,
                  "provider_key": "",
                  "provider_id": "",
                  "error": ""
                  
                  }
                
files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1 Uncaught TypeError: Cannot read property 'entryId' of null
    at HTMLLIElement.<anonymous> (files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1)
    at Function.each (head-5YvgxlJ81lsF74KwR1f3YQ2.js?ver=9.0.0.300:2)
    at i.fn.init.each (head-5YvgxlJ81lsF74KwR1f3YQ2.js?ver=9.0.0.300:2)
    at Object.rt [as addRowHandlers] (files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1)
    at n (files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1)
    at e (files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1)
    at s (files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1)
    at Object.c (files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1)
    at Object.complete (files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1)
    at c (head-5YvgxlJ81lsF74KwR1f3YQ2.js?ver=9.0.0.300:2)
(anonymous) @ files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1
each @ head-5YvgxlJ81lsF74KwR1f3YQ2.js?ver=9.0.0.300:2
each @ head-5YvgxlJ81lsF74KwR1f3YQ2.js?ver=9.0.0.300:2
rt @ files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1
n @ files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1
e @ files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1
s @ files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1
c @ files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1
(anonymous) @ files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1
c @ head-5YvgxlJ81lsF74KwR1f3YQ2.js?ver=9.0.0.300:2
fireWith @ head-5YvgxlJ81lsF74KwR1f3YQ2.js?ver=9.0.0.300:2
b @ head-5YvgxlJ81lsF74KwR1f3YQ2.js?ver=9.0.0.300:2
(anonymous) @ head-5YvgxlJ81lsF74KwR1f3YQ2.js?ver=9.0.0.300:2

Error parseJSON: 

                  {
                  "entryType": "folder",
                  "access": 0,
                  "create_by_id": "9db9cd5e-cd54-11e6-a7a1-0242ac12000427/02/2017 01:3116/03/2017 20:51trueLog0,
                  "provider_key": "",
                  "provider_id": "",
                  "error": ""
                  
                  }
                
files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1 Uncaught TypeError: Cannot read property 'id' of null
    at HTMLAnchorElement.<anonymous> (files-Ra4sMIpuXwsVl52tbUKL2w2.js?ver=9.0.0.300:1)
    at HTMLUListElement.dispatch (head-5YvgxlJ81lsF74KwR1f3YQ2.js?ver=9.0.0.300:2)
    at HTMLUListElement.a.handle (head-5YvgxlJ81lsF74KwR1f3YQ2.js?ver=9.0.0.300:2)

...

Any ideas? It seems as if something is wrong in the "create_by_id" value. The error does not occur in FireFox (52.2.0) and I can open/edit files/folders just fine.

Maxim
Posts: 1790
Joined: Tue Oct 11, 2016 2:34 pm

Re: Problem parsing JSON in Chromium 59

Post by Maxim » Thu Jun 29, 2017 11:13 am

Hello PurpleAlien!
We tried to reproduce the issue but had no luck. Please try to clean browser's cache.

PurpleAlien
Posts: 2
Joined: Thu Jun 22, 2017 11:25 pm

Re: Problem parsing JSON in Chromium 59

Post by PurpleAlien » Fri Jun 30, 2017 5:50 pm

Hi,

That was one of the fist things I tried, no luck.
Not sure what additional info I can give. The client browser is running on Gentoo Linux, but that shouldn't make a difference.

I'll see if I can gather more intel.

Maxim
Posts: 1790
Joined: Tue Oct 11, 2016 2:34 pm

Re: Problem parsing JSON in Chromium 59

Post by Maxim » Mon Mar 19, 2018 10:25 am

Hello!
Please try to reproduce it in Community Server ver.9.6

Post Reply