1.1.0-beta.1

First beta release for 1.1.0. This release moves the integration closer to Nextcloud's native APIs, adds optional full-text indexing of pad content and tightens installation, migration and lifecycle behaviour.

Highlights

• Search inside pads. With Nextcloud's Full Text Search apps and a configured backend, .pad files can now be found by their stored plain-text content. Frontmatter, pad ids and snapshot HTML are not indexed, and per-storage indexing settings are respected.
• Native Nextcloud Viewer integration. The Viewer is registered through the supported @nextcloud/viewer API, while public shares use Nextcloud's own opening and file-action flows instead of custom route and DOM handling.
• Reliable first installation. The .pad extension, MIME part and Etherpad display name are registered when the app is installed. The icon stays inside the app rather than modifying Nextcloud's signed core files.
• Safer legacy imports. Importing protected Ownpad group pads is disabled by default and can be enabled explicitly by an administrator where the Etherpad server is not shared with another group-pad creator.

Further changes

• Protected-pad sessions now last six hours for authenticated users and three hours through public shares.
• External pad snapshots preserve text containing the snapshot marker lines and no longer create repeated file versions for an unchanged pad.
• Cleanup after partially failed creation, initialisation, template materialisation and restoration is more consistent and concurrency-safe.
• The minimum supported Nextcloud version is now 31.0.9; Nextcloud 32, 33 and 34 remain supported.
• DOMPurify updated to 3.4.15.
• CI coverage now includes the exact supported Nextcloud floor, PHP 8.1 through 8.5 and a full Nextcloud 34 + Elasticsearch indexing stack.

Existing pads on an already configured Full Text Search installation can be indexed immediately with:

php occ fulltextsearch:index '{"provider":"files","force":true}'