Hello, I’m a student and now I’m working on a project about using collaboraonline to edit pages online and embed them inside my own web pages. The version is 6.4 or the following version, now there is a question after I modify the source file PPT from the backend, why the front-end online editing PPT page can not take the initiative to appear after the modification of things, but to manually refresh it, which will affect the use of other users to modify, this is very important for my project, I hope to get your answer, thank you, I wish you a happy day
Hii @Yaya2003
Thanks for your question and great to hear you’re working on a project using Collabora Online!
What you’re experiencing is expected behavior: Collabora Online doesn’t automatically reload or reflect backend file changes in real-time. Once a document is loaded in the editor, it stays in memory for that editing session. If the file is changed on the backend, users won’t see those updates unless they manually refresh the document there’s no built-in auto-sync with backend changes.
This design is intentional to avoid unexpected data loss while users are actively editing, especially in collaborative environments.
That said, we understand that for certain workflows (like yours), auto-refresh or file change detection would be helpful.
If you’d like to explore improving this or contributing to the project, feel free to check out:
- The developer site: https://collaboraonline.github.io/
- The source code and issue tracker on GitHub: https://github.com/CollaboraOnline/online
Happy hacking,
Darshan 
1 Like
Forgive me for not being very familiar with these matters. May I ask, if I really want to achieve the function of modifying source files in the backend and having the frontend online editing page automatically render that page, where should I start? How should I proceed with the modifications? I hope to hear a professional response.
Since 24.04, by default, Cool saves documents that have unsaved changes every 5 minutes, and idle documents every 30 seconds. Saves are nearly instantaneous for users as saving is done out of the document process. This can be changed in , with the settings and ./etc/coolwsd/coolwsd.xmlautosave_duration_secsidlesave_duration_secs
Can this save be rendered on the front-end page?
Or which latest version can solve this problem?