-
Suggestion
-
Resolution: Fixed
-
1
-
Issue Summary
Currently, on startup the Companion App will remove all attachments from its temporary directory. This is to prevent temporary files building up and taking up too much space.
However, some users would prefer to have more control over when these files are deleted. We could provide a configuration option in the Companion menu such as "Clear temporary files on startup" that defaults to selected. If the user unticks this option then we would no longer perform the clear out of the temporary directory.
This suggestion is important in cases when the user did not upload changes, but it has saved them. And because of that, his changes will be gone, and we will not be able to recover them.
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[CONFSERVER-58425] Companion App should provide a configuration option to prevent clearing files on startup
For the next version of Companion, it will only clear out files which were modified over 60 days ago. This ticket will be updated when the new version of Companion is released
Well its apperently a bug in the design from the beginning.
Or would you consider the same beahviour in confluence as an intended behaviour as well.
E.g. restarting confluence server would wipe out all existing drafts?
This is not a bug, it is intended behaviour in order to prevent temporary files filling up the user's hard drive. However we will consider adding a menu option to switch this functionality on/off.
One way to mitigate this would be to switch off "Launch on Startup" for Companion as the files are cleared when the Companion App starts. This would allow the user to save the temporary files before manually starting the Companion App.
This is a very common scenario for us. Because restarting your computer will (of course) restart the companion application and empty all files in its folder...
A better solution would be to ask the user which file(s) to be deleted at companion startup or delete the files after a time period instead (a month or so).
======
Scenario: I started doing a report by editing a excel-file, using the edit in excel-feature in confluence. The file is opened in excel and I have been working on it for a couple of hours, and saving it continously as you don´t want anything to be lost. Due to some other issues I had to do other stuff, including restarting my computer. Next day I wanted to continue in updating my report.
My first thought was just to open excel, browse for the last used files, and continue my work from there. (and then upload the file manually since I know that the browser connection for the companion app is gone, once you close the browser.)
Everything looking good in excel, it remembered I used and saved the file yesterday, however clicking on the file, it reveals that the file is gone!
A fix for this issue is available in Companion 1.0.0. View the Release Notes to see what other issues are resolved.
If Companion is installed via the MSI, then it will need to be manually updated to the new version.