All plugins

DSH / BUNDLE / CLIENT-UI

@dake6767/dsh-onlyoffice

v0.1.9dake6767 / dsh-onlyofficee358808cb2

InstallableBundlesUI & client pluginsCommunity · Topic auto-analysisWeb UI

Overview

@dake6767/dsh-onlyoffice

DSH web plugin: open .docx/.xlsx/.pptx from the sidebar file manager in an embedded OnlyOffice editor (static SDK, no Document Server).

README / EN

Package documentation

Registry summary

DSH web plugin: open .docx/.xlsx/.pptx from the sidebar file manager in an embedded OnlyOffice editor (static SDK, no Document Server).

dsh.pub verifies the pinned bundle contract, runtime facts, and distribution semantics. The complete README remains in the source repository.

Read the full README on GitHub

LIMITATIONS

Known limitations

### Troubleshooting: "host SDK route unreachable" on a space page DSH spaces can serve the workspace at `/app/<spaceId>/`. On such a page the plugin routes are reachable **only under that prefix**; the same routes at the origin root are rejected by the connection fence with `403 Forbidden`. The client therefore probes the candidates at startup (page directory → origin → root-relative) and reuses whichever answers `GET …/status` with JSON. Run this in the page console to see exactly what each base returns: ```js await window.__dshooProbe() ``` It reports HTTP status, content-type, timing and a body prefix for both `/status` and the SDK `api.js`, so `403 / text/plain` (fence) is easy to tell apart from `200 / text/html` (SPA fallback) or a timeout.