We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello!
"OnlyOffice Document Editor handles the most popular file formats", but i can't change seahub behaviour to view/edit them with OnlyOffice.
It would be great, if i could associate each file extension with editor/viewer (seahub internal, onlyoffice or other) on seahub settings page.
Something like this: [file extension] - [file icon] - [editor: internal | onlyoffice | ... ] - [open mode: edit | view-only]
Thank you!
https://helpcenter.onlyoffice.com/ONLYOFFICE-Editors/ONLYOFFICE-Document-Editor/HelpfulHints/SupportedFormats.aspx
Seafile CE 6.3.2
The text was updated successfully, but these errors were encountered:
Hello you can custom file extension in seahub_settings.py
https://manual.seafile.com/deploy/only_office.html
Sorry, something went wrong.
the setting is ignored
ONLYOFFICE_FILE_EXTENSION = ('doc', 'docx', 'ppt', 'pptx', 'xls', 'xlsx', 'odt', 'fodt', 'odp', 'fodp', 'ods', 'fods', 'pdf')
Recreated seafile docker container -> still opens in the seafile's own preview.
No branches or pull requests
Hello!
"OnlyOffice Document Editor handles the most popular file formats", but i can't change seahub behaviour to view/edit them with OnlyOffice.
It would be great, if i could associate each file extension with editor/viewer (seahub internal, onlyoffice or other) on seahub settings page.
Something like this:
[file extension] - [file icon] - [editor: internal | onlyoffice | ... ] - [open mode: edit | view-only]
Thank you!
https://helpcenter.onlyoffice.com/ONLYOFFICE-Editors/ONLYOFFICE-Document-Editor/HelpfulHints/SupportedFormats.aspx
Seafile CE 6.3.2
The text was updated successfully, but these errors were encountered: