How to avoid creating the folder "Documents for OnlyOffice"? iPad

Docs
1

How can I disable OnlyOffice from creating the folder “Documents for OnlyOffice”? This is causing chaos par exellance…

I am working on Docx on different platforms in specific folders. I want the structure kept as it is including all docs.

OnlyOffice creates the unwanted folder “Docs for OnlyOff.” and copies the files into this folder.

So, how can I set up OnlyOffice to avoid this misbehaviour so that it works like every other known program.

I want to open e.g. myBooks/book3.docx in OnlyOffice and when I close the document it will be saved into the folder myBooks/boo3.docx (incl. the alert “overwrite yes/no”.

Thanks for your patience.

take care

2

Hello @Wizzarts
Please let us know versions of the app and the device itself. Additionally record a video file of the issue. I’ve checked file file creation\opening on the iOS device using the mobile app, but didn’t notice described situation. I may have tested it incorrectly, so please provide more details.

3

Thanks For your reply.

I already uninstalled OnlyOffice. I re-installed it on my iPad Gen 9 latest OS and the first thing I found was the folder “Documents by OnlyOffice”.

The Docx files are now opened in Pages when double clicking them. In OnlyOffice the folders are not shown at all. I cannot open files the normal way by selecting a folder on my iPad and the loading it. The only folder shown when using the iPad button is “Documents by OnlyOffice”.

Using the 3-dot button I can import files just to find them in the DbOO folder.

No more support needed - I uninstalled the whole thing again and am now using a proper working alternative.

Thanks for your patience and good-bye

4

Ah, now I understand. Thank you for the provided details, we will check the situation in any case and contact you once we have something to share.

6

Hello @Wizzarts
The described behavior is expected. The app creates a folder so that new files have a place to be stored. There is no way to change this behavior.
Sorry for the inconvenience.

7

This is the exact problem… It sounds great in the first place but has an enormous downside.

Importing a file and then moving it back to the correct folder is some steps too much and has caused chaos and data loss.

This is the “your document” folder found in windows that no one is using… :smiley:

It is a good idea to have one place for the files when using only “OnlyOffice”.

But when interchanging files forth and back it is a NO-GO.

Maybe, you re-think the issue and allow the using to change this bahaviour in the “settings” when needed.

Take care

8

ERROR:

Maybe, you re-think the issue and allow the user to change this bahaviour in the “settings” when needed.

10

Hello @Wizzarts
Thank you for the provided details. We need some time to discuss your suggestion internally.
I will update this thread once we have something to share.

12

Hello @Wizzarts
We have added your suggestion to internal tracksystem, we have started working on it.
I will contact you once we have something to share.

1 Like
13

Hi Alexandre,

please let me help you on this by describing what I exactly meant.

As stated before it is a goog idea to have the “one” folder for all docs.

But:

When there is a given folder structure the “documents by OnlyOffice” is not needed. Think about a common Windows system.

You have a structure on drive g:/ for book projects etc… On drive e:/ are your business files from taxes to correspondence with companies.

When opening a doc nested on drive g:/ the file itself will not be moved. I will be opened and afterwards be saved on the exact same location with the exact same name, - including a msgbox asking for overwrite, new name or abort.

Opening a file outside work in two ways:

  1. You go the the folder where the file is nested and open with O.O or something similar.
    or
  2. You start OnlyOffice and within O.O you navigate to the folder where the file is placed.

I hope this makes things a bit easier to understand.

14

Thank you for additional details, I believe we are on the same page now.
Right now, I cannot provide ETA or the form of the implementation of your suggestion, but we already started our work. I will keep you posted once we have something to share.