Skip to content

fix(filesplugin): file actions invisible on NC33+ (registry mismatch, #848)#855

Draft
oleksandr-nc wants to merge 2 commits intomainfrom
fix/848-fileaction-registry-mismatch
Draft

fix(filesplugin): file actions invisible on NC33+ (registry mismatch, #848)#855
oleksandr-nc wants to merge 2 commits intomainfrom
fix/848-fileaction-registry-mismatch

Conversation

@oleksandr-nc
Copy link
Copy Markdown
Contributor

@oleksandr-nc oleksandr-nc commented Apr 30, 2026

Fixes #848.

AppAPI bundles @nextcloud/[email protected], which still uses the legacy window._nc_fileactions array, while NC33+ ships @nextcloud/[email protected] and reads from the new versioned scoped registry at window._nc_files_scope.v4_0.fileActions - so file actions registered by ExApps land in a registry the Files app never reads, and never become visible.

@oleksandr-nc oleksandr-nc force-pushed the fix/848-fileaction-registry-mismatch branch 5 times, most recently from 0310687 to fa43b5d Compare April 30, 2026 12:17
@oleksandr-nc oleksandr-nc force-pushed the fix/848-fileaction-registry-mismatch branch from fa43b5d to 9aae687 Compare April 30, 2026 12:23
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.

FileActionMenu entry does not appear

1 participant