Try the fastest and simplest way to install ONLYOFFICE

Bad JSON formatting, Chromium v64

Any issues about docs (uploading, editing and etc.)

Bad JSON formatting, Chromium v64

Postby sebmacc » Wed Mar 07, 2018 2:21 pm

Hello,

I have a problem with a freshly-installed OnlyOffice instance, specifically in the documents module, when clicking on a document.
Visually, I get no effect when clicking on any document, with the left mouse button or with the right button.
The regular browser context menu is not displayed either, so the event is catched.

I have this problem with Chromium 64.0.3282.186 on Linux (NixOS).
I don't have this problem with Firefox 58.0.2.
Colleagues of mine don't have this problem with Google Chrome 64.0.3282.186, on Linux and on Windows.

However, I have the following error in the console:
Code: Select all
Error parseJSON:

                  {
                  "entryType": "file",
                  "access": 0,
                  "create_by_id": "cb973ca0-6b31-4a5f-815e-8ab2d9b7a3ce",
                  "create_on": "07/03/2018 12:27",
                 
                  "modified_on": "07/03/2018 12:27",
                  "shared": trueONLYOFFICE Sample Document.docx55,52 koNone11,
                  "provider_key": "",
                  "error": ""
                 
                  }

... followed by another error, which differs depending on the action I'm trying to do.

I've tried digging, and I have found that this JSON data is in the exact same format in the DOM:
Code: Select all
<input type="hidden" name="entry_data" data-id="4" value="
                  {
                  &quot;entryType&quot;: &quot;file&quot;,
                  &quot;access&quot;: 0,
                  &quot;create_by_id&quot;: &quot;cb973ca0-6b31-4a5f-815e-8ab2d9b7a3ce&quot;,
                  &quot;create_on&quot;: &quot;07/03/2018 12:27&quot;,
                 
                  &quot;modified_on&quot;: &quot;07/03/2018 12:27&quot;,
                  &quot;shared&quot;: trueONLYOFFICE Sample Document.docx55,52 koNone11,
                  &quot;provider_key&quot;: &quot;&quot;,
                  &quot;error&quot;: &quot;&quot;
                 
                  }
                ">


We can see that some fields values are incorrectly written inline after the "shared" boolean value (title, content_length, file_status, version, version_group).

With Firefox, the JSON is correct :
Code: Select all
<input name="entry_data" data-id="4" value="
                  {
                  &quot;entryType&quot;: &quot;file&quot;,
                  &quot;access&quot;: 0,
                  &quot;create_by_id&quot;: &quot;cb973ca0-6b31-4a5f-815e-8ab2d9b7a3ce&quot;,
                  &quot;create_on&quot;: &quot;07/03/2018 12:27&quot;,
                 
                  &quot;modified_on&quot;: &quot;07/03/2018 12:27&quot;,
                  &quot;shared&quot;: true,
                  &quot;title&quot;: &quot;ONLYOFFICE Sample Document.docx&quot;,
                  &quot;content_length&quot;: &quot;55,52 ko&quot;,
                  &quot;file_status&quot;: &quot;None&quot;,
                  &quot;version&quot;: 1,
                  &quot;version_group&quot;: 1,
                  &quot;provider_key&quot;: &quot;&quot;,
                  &quot;error&quot;: &quot;&quot;
                 
                  }
                " type="hidden">


I don't know how this input value is generated, I guess it is generated dynamically from javascript...

Moreover, I don't have the icons. The icon element HTML on Chromium is:
Code: Select all
<div class="thumb-file" title="ONLYOFFICE Sample Document.docx"></div>

... whereas on Firefox it is:
Code: Select all
<div class="thumb-file ftFile_32 ft_Docx" title="ONLYOFFICE Sample Document.docx"></div>



This issue looks similar to another problem from a few months ago : viewtopic.php?f=3&t=10029

Clearing the cache didn't help.
Starting a brand new chromium profile with "chromium --disable-extensions --disable-plugins --user-data-dir=foobar" didn't help either.
sebmacc
 
Posts: 1
Joined: Wed Mar 07, 2018 1:16 pm

Re: Bad JSON formatting, Chromium v64

Postby Maxim » Mon Mar 19, 2018 8:02 am

Hello sebmacc!
We will try to reproduce this issue.
I will inform you as i get information.
Maxim
 
Posts: 1743
Joined: Tue Oct 11, 2016 2:34 pm

Re: Bad JSON formatting, Chromium v64

Postby Maxim » Mon Mar 19, 2018 10:24 am

Hello ebmacc!
Try to reproduce it in Community Server ver.9.6
Maxim
 
Posts: 1743
Joined: Tue Oct 11, 2016 2:34 pm


Return to Documents

Who is online

Users browsing this forum: No registered users and 4 guests