Editor update

Can you please provide a screen recording of the issue reproduction with Console tab of DevTools opened?
Generally, nothing should be added to Vue application config after the update


The content of the pop-up prompt is (Editor version has been updated. The page will be reloaded to apply the changes.)

First of all, please try updating to newer 8.1.1 version, but make sure that the old configs are not preserved after the update as preserving them may lead to such an issue. If the issue stays after the update, please reproduce it with DevTools → Console tab opened in particular and send us the screenshot of it

Thank you for your reply. I have confirmed that the version I am using is 8.1.1. There were screenshots taken during the above reply process, and I used a brand new server to deploy the service.

Alright. So please provide the screenshot of the Console tab in particular during the issue reproduction

I have provided relevant screenshots in the above reply. Please pay attention to the content and reply as soon as possible. Thank you.

I have noticed an interesting phenomenon where I deployed version 8.1.1.26 of DocumentServer using Docker. However, when my application switches back to the self compiled version 7.5.1.0 of DocumentServer deployed on another server after using that version, it will display a prompt indicating that the editor has been updated. Does this phenomenon involve any configuration? Please let me know.

Hello, I mean this particular Console tab which is highlighted on the screenshot, please see for reference:

Earlier you provided screenshots of Network tab in particular.
As for your last message, this issue usually occurs when old configs are preserved when switching between versions. Old configs should not be preserved (as then in ds-docservice.conf for example you’ll have wrong version of Document Server specified).
It is probable that the issue that you faced is connected with this as a whole.

This request address( http://test.jckj.group/onlyoffice/8.1.1-26/doc/2dbd1a9ddf79486c8a4afbfc34d22716/c/?shardkey=2dbd1a9ddf79486c8a4afbfc34d22716&EIO=4&transport=polling&t=P4rs -Gv. 0&sd=2Aj4WsPgeUwvzZApAAAG), the previous version 7.5.1 did not have a version number, but after switching to the new version, it has always had the version numbers 8.1.1-26. This version number causes this prompt, and I am not sure how to clear this setting.

Is it convenient to reply to my question recently? I have not been able to solve this issue independently. I compared the requests of two projects on my end for the same only office document server service. Normally, when a project requests document server, the request address is attached with sharedkey. How is this parameter controlled?

Hello, sorry for the late reply, please clarify, do you use proxy in front of Document Server? If so, which one?

image

Please refer to this link’s content in terms of proxy settings: document-server-proxy/nginx/minimal.conf at master · ONLYOFFICE/document-server-proxy · GitHub
Configure proxy according to our example

Sorry,The previous screenshot shows the reverse proxy used by nginx for DocumentServer in my project, and DocumentServer has also configured nginx proxy. The content is as follows:
map $http_host $this_host {
“” $host;
default $http_host;
}
map $http_x_forwarded_proto $the_scheme {
default $http_x_forwarded_proto;
“” $scheme;
}
map $http_x_forwarded_host $the_host {
default $http_x_forwarded_host;
“” $this_host;
}
map $http_upgrade $proxy_connection {
default upgrade;
“” close;
}
proxy_set_header Host $http_host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $proxy_connection;
proxy_set_header X-Forwarded-Host $the_host;
proxy_set_header X-Forwarded-Proto $the_scheme;
server {
listen 0.0.0.0:80;
listen [::]:80 default_server;
server_tokens off;
rewrite ^/OfficeWeb(/apps/.*)$ /web-apps$1 redirect;
location / {
proxy_pass http://localhost:8000 ;
proxy_http_version 1.1;
}
}

I used this nginx configuration on version 7.5.1 of DocumentServer, and after switching to 8.1.1, a pop-up message will appear indicating that the editor had been updated and the page would be reloaded to apply the changes

Please give us the link of your 8.1.1 Document Server, so we could check ourselves

Sorry, my document server is deployed on an internal network server and cannot be used externally. Can I provide you with the compiled files and send them to your email?

Thank you for your patient response. Currently, I have resolved the issue. Due to the caching of JS files by my external nginx proxy, the API. js always retrieves the old version, causing conflicts with the new version and resulting in pop-up prompts.

Hello, thank you for sharing, glad to know that the issue has been resolved