Custom file actions wrong when navigating back to root via breadcrumbs

Where best to report bugs?

In v30, after loading the root file listing, custom file actions are added correctly via execution of the enabled() function, and they continue to be correct as one drills down into subdirectories, but when returning to the “All files” root view, all files/nodes at the root view have the custom actions according to the folder one just returned from.

E.g. if the root has two directories “foo” and “bar” and the custom file action “doFoo” is added to the “foo” directory and “doBar” is added to the “bar” directory, and one drills down into “bar” and then clicks “All files” in the breadcrumbs, both “foo” and “bar” have the action “doBar”.

If one reloads the view, the custom actions are fixed.

Debugging shows that enabled() is being called only for the “bar” folder but not “foo” when the root view is returned to via breadcrumbs from within the “bar” subtree.

Thanks for your report.

Please log an issue at GitHub - nextcloud/server: ☁️ Nextcloud server, a safe home for all your data