Skip to content

todo: update to v33#372

Draft
otherwiseGG wants to merge 8 commits into
nextcloud:masterfrom
otherwiseGG:master
Draft

todo: update to v33#372
otherwiseGG wants to merge 8 commits into
nextcloud:masterfrom
otherwiseGG:master

Conversation

@otherwiseGG
Copy link
Copy Markdown

Hiya! I started working on moving this project over to v33. This is some beginning that makes the Plugin comaptible with the recent changes in v33. There are however still alot of issues with it, but atleast it doesnt complain anymore.

Nextcloud 33 query API compatibility
Add a small query helper that abstracts executeQuery / executeStatement vs legacy execute().
Update session, change, lock, and IPC storage paths to use the compatibility layer instead of direct deprecated calls.

Supported format auto-configuration
Restrict community auto-configuration to the format set supported by the bundled document server.
Preserve ONLYOFFICE’s discovered format matrix, but filter default/editable selections to known-safe extensions.
Re-sync existing community-document-server installs when unsupported formats are currently enabled, preventing invalid documentType configs from being generated.

Copilot AI and others added 4 commits May 11, 2026 09:32
…n-version

Normalize document route paths to avoid malformed conversion URLs
…eter

Fix Nextcloud 33 DB compatibility and limit community auto-config to supported editor formats
Copilot AI review requested due to automatic review settings May 11, 2026 10:32
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR begins the migration of the documentserver_community app toward Nextcloud v33 compatibility by introducing a DB query compatibility layer and updating several persistence layers to use it, alongside adjustments to ONLYOFFICE auto-configuration and document file route handling.

Changes:

  • Add DB\QueryHelper to abstract executeQuery/executeStatement (v33+) vs legacy execute() usage, and migrate session/change/lock/IPC DB access to it.
  • Update SessionManager to accept an IIPCFactory and clean up IPC channels when expiring sessions.
  • Restrict/normalize ONLYOFFICE community document server auto-config formats and normalize generated documentFile paths.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.

Show a summary per file
File Description
tests/Channel/SessionManagerTest.php Updates test setup/teardown for new SessionManager constructor and query execution helper.
lib/OnlyOffice/AutoConfig.php Adds supported-format filtering and sync behavior for community document server installs.
lib/IPC/DatabaseIPCBackend.php Switches DB operations to QueryHelper for v33 query API compatibility.
lib/Document/LockStore.php Switches lock persistence queries to QueryHelper.
lib/Document/ChangeStore.php Switches change persistence queries to QueryHelper and handles MAX() returning null.
lib/DB/QueryHelper.php Introduces the compatibility helper for query execution and fetching across Nextcloud versions.
lib/Controller/DocumentController.php Normalizes incoming file paths to be relative (strips leading /).
lib/Controller/ConvertController.php Generates relative path values for documentFile route usage.
lib/Channel/SessionManager.php Migrates queries to QueryHelper and injects IIPCFactory for channel cleanup on session expiry.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@otherwiseGG otherwiseGG marked this pull request as draft May 11, 2026 11:04
Copilot AI and others added 4 commits May 11, 2026 14:48
…elogs

Align controller endpoint annotations with Nextcloud v33 attribute requirements
…-options

Normalize controller responses and preserve PDF default format in v33
@otherwiseGG
Copy link
Copy Markdown
Author

In the current Version, we're able to get basic Functionalities back without Complaining. We are currently trying to get PDF Read & Edit back on track.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants