Fixes the problem that binding with SharePoint using New-SPWOPIBinding
is only possible when specific extensions or applications are specified.
Trying to bind all information from discovery resulted in error:
New-SPWOPIBinding : One or more of the WOPI bindings specified in
New-SPWOPIBinding already exist. The operation has been cancelled.
Change-Id: I5675c4cee8b68b81b5c0971a5dc577f653a1ae5b
Reviewed-on: https://gerrit.libreoffice.org/c/online/+/97063
Tested-by: Jenkins
Tested-by: Jenkins CollaboraOffice <jenkinscollaboraoffice@gmail.com>
Reviewed-by: Andras Timar <andras.timar@collabora.com>
... because lotuswordpro filter is not present in MPLv2-only core builds
Change-Id: I100e886273f8b7fd38887576c2d29fad4c69b2e7
Reviewed-on: https://gerrit.libreoffice.org/79683
Tested-by: Jenkins CollaboraOffice <jenkinscollaboraoffice@gmail.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
Tested-by: Tor Lillqvist <tml@collabora.com>
(cherry picked from commit d7813989913e95cefc8484d6d2af965ed5752588)
Add an entry to discovery.xml with the urlsrc where capabilities end
point can be found. Use json format to send back the feature list.
Change-Id: I390a53d956d53ca79e5a8090aead7f4131ec4ca0
